I have experienced a number of problems with the VSS integration. Some are clearly bugs, others are the lack of very important features:
(1) Bug: Right clicking on a filename in the project window or usages window and choosing a source-safe operation (such as check-out) will try to check out the file of the current-editor window instead of the file clicked on, unless there are no editor windows open. (2) Bug: The source-safe menu displays check-in, check-out, and add as options, even if the file is already checked in, already checked out, or already added to the source-safe tree. (3) Lack of Feature: VSS does not color-code the files in accordance with their checked-in/checked-out state. (4) Lack of Feature: Adding a file to the project does not prompt to add it to source-safe. (5) Lack of Feature: Removing a file from the project does not prompt to remove it from source-safe. (6) Lack of Feature: Renaming or moving the package of a file does not properly update to source-safe. Moving a file should prompt to move the file in source-safe, and then check-out the file from the new location. If the file has already been checked-out, it should move the file in source-safe and in the local directory structure, and should update the check-out-to location of the file such that it will be checked back in from the new location. Note that removing and adding the file from source-safe is not sufficient, as the file may be a shared-file, and removing and adding would lose the shared-state. (7) Lack of Feature: When getting latest version, IntelliJ should also perform a directory-structure diff afterwards and show all the files that exist in only the local directory or the source-safe directory, but not both. A contextual menu should allow the user to choose "add to sourcesafe" or "delete from local directory" for each of the files. This would facilitate users in recovering correctly from name changes, file movements, and other refactorings by their peers. Other Points: (1) It was not clear to me whether IntelliJ is correctly deleting the old .class file from the output directory when a class is renamed or moved. Is this the case? (2) It would be highly convenient if IntelliJ could automatically e-mail a list of co-workers with refactoring information when certain refactorings are made, or at least keep a list of refactoring descriptions that an engineer can e-mail to his peers. This is especially important for teams using source-control that might get confused when a file is renamed, or moves directories. It is most important to have a list of file movements, file renames, and file additions and deletions. Changes to the structure of the code inside is important, but not as urgent. I hope these features can make it into the product soon, as I am trying to convince my company to switch to IntelliJ, and inadequate SourceSafe integration (as well as lack of multiple-window support) are their main reasons for not switching. -Dwight Rodgers _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
