New Clearcase Plugin Feedback
Hello Michael,
I've installed Selena 6433 and tried the new clearcase integration, so here are my first impressions and some bugs i encountered :
1 - You are definitely on the right track :)
2 - In my case, my IntelliJ project (ipr) has like 9 modules. Each module is inside a separate view. This means that when i checkin multiple files at a time from a change list for example, i potentially check them in differents views. In UCM, each user view has a 'current activity' defined. There should be a way to show and possibly to change/create at commit time those CC activities on a per/module basis. Like a panel with the following informations:
3 - Bug : if i tried to "add to VCS" a file whose parent directory is not versioned, i have a "not vob object" for the parent
directory at commit time.
4 - Maybe i missed something, but when i have a list of "unversioned files", and i say "add to VCS" to one of them, i cannot
change my mind afterward, and make it go back in the "unversioned files" list, i can only "Rollback" the file, which deletes it from the hard drive.
Hope this helps, great work by the way ! Keep it up
Gilles
Please sign in to leave a comment.
Another bug : i only work with snapshot views. When i "Update Project", i have the following error :
Error:You can not update a dynamic view: Error executing cleartool update : cleartool: Error: 'c:\progra1\jetbra1\intell~2\bin' is not a valid snapshot view path.
Gilles
Another weird thing :
In my .ipr, there are entries (ClearCasePersistencyNewFile) under component ClearCase with absolute references to files on my hard drive. Could we have an option to make that into the .iws instead, because the .ipr is shared by many developers ?
Gilles
Dear Gilles,
GP> In my .ipr, there are entries under component ClearCase with
GP> absolute references to files on my hard drive. Could we have an
GP> option to make that into the .iws instead, because the .ipr is
GP> shared by many developers ?
Sorry for the silence, I had a terrible flu all previous week. I'll answer
all your questions a little bit later, with fixes in mind :-).
best wishes,
Michael Gerasimov,
JetBrains Omea Developer
Dear Gilles,
GP> 1 - You are definitely on the right track :)
Thanx!
GP> 2 - In my case, my IntelliJ project (ipr) has like 9 modules. Each
GP> module is inside a separate view. This means that when i checkin
GP> multiple files at a time from a change list for example, i
GP> potentially check them in differents views. In UCM, each user view
GP> has a 'current activity' defined. There should be a way to show and
GP> possibly to change/create at commit time those CC activities on a
GP> per/module basis. Like a panel with the following informations:
GP> =================================================================== GP> _____ ______ GP> Activity module A : "performance enhancement" | Add | |Change| GP> _____ ______ GP> Activity module B : "Bug fix" | Add | |Change| GP> GP> .... GP> =================================================================== GP> ]]>
I caught the idea, thanx!
GP> 3 - Bug : if i tried to "add to VCS" a file whose parent directory
GP> is not versioned, i have a "not vob object" for the parent directory
GP> at commit time.
Fixed, to appear in the next EAP.
Now when you add some unversioned file to the list of new files
(to be added to the vcs) all its unversioned parent folders get NEW status
as well and will be
added to the repository independently of whether they are explicitely checked
in the
COMMIT dialog.
GP> 4 - Maybe i missed something, but when i have a list of "unversioned
GP> files", and i say "add to VCS" to one of them, i cannot
GP> change my mind afterward, and make it go back in the "unversioned
GP> files" list, i can only "Rollback" the file, which deletes it from
GP> the hard drive.
Fixed, to appear in the next EAP.
best wishes,
Michael Gerasimov,
JetBrains Omea Developer
Dear Gilles,
GP> Another bug : i only work with snapshot views. When i "Update
GP> Project", i have the following error :
We have a tough time here with the CCase server trying to make it work properly.
If we manage
to clean all its internals, I'll fix this today. That was just a typo in
the code.
best wishes,
Michael Gerasimov,
JetBrains Omea Developer