Where can I get feedback on SourceSafe integration?
Hi,
I've bought a personal licence for previous versions of IDEA, and am intending to upgrade to IDEA 6. I've recently changed job and would like to encourage use of IntelliJ there. Unfortunately, they use Visual SourceSafe 2005 and I can't get it to work with IDEA 6 (or 5.1.2). I've tried posting here several times, maybe it's the wrong place.
Can somebody help me find a solution? Where should I post VSS questions?
Thanks,
Chris
Please sign in to leave a comment.
Hello Christopher,
IDEA 6.0 has been succesfully tested with VSS 2005. What exactly does not
work in your setup?
Thanks,
Vladislav Kaznacheev
Project Manager, IntelliJ IDEA
http://www.jetbrains.com
"Develop with Pleasure!"
When I open a project where I've tried to configure VSS integration, an error message dialog appears (titled "Could not start process") with the following text :
com.intellij.openapi.vcs.VcsException: Incorrect username or password
The login and password are correct (they work with Eclipse and the "official" VSS client).
Where I'm working, there are multiple projects, each one with a dedicated VSS project on the server. I have setup each relevant VSS project as a module within the same IDEA project (because there are code dependencies). Each VSS project has a different srcsafe.ini file (because the repositories are located on a network share called S:\vss, for example DB.PORTAL and DB.VOLCANO subdirectories). The dialog box for version control configuration in IDEA doesn't seem to allow different settings per-module (if I change the path to srcsafe.ini for one module, the change is applied to the second module too).
The VSS 2005 client ("ssexp.exe") doesn't work correctly unless you copy the shortcut icon under windows and edit the shortcut to add the /D parameter after ssexp.exe, as in /DPROJECTNAME ... where PROJECTNAME has a different value for each project. Is this sort of thing handled by the IDEA VSS integration? It looks like I can't specify this parameter for ssexp.exe, I can only specify the path to ssexp.exe. The /D parameter apparently specifies which DB.* subdirectory the client should connect to, as defined in the file "S:\vss\srcsafe.ini".
I know it's a strange setup, but I can't influence what's already been decided (otherwise I'd be pushing for Subversion... :)).
Thanks,
Chris
Attachment(s):
idea_vcc.PNG
windows_shortcut.PNG
eclipse_vss_mapping.PNG
eclipse_vss_info.PNG
eclipse_vss_configuration.PNG
Did my feedback help or do you need additional information?
Is any progress being made on this subject?
Thanks,
Chris
I don't use VSS, but it might help for you to separate the issues.
It sounds like one issue is that IDEA doesn't support VSS config per module.
You said you had to add everything into one project due to code depedenciees.
But is there one of these VSS projects which is independent? Can you add this as an IDEA project and does VSS integration work in this case.
It is unclear from your descrption if the proble is only because you have multiple VSS projects in one IDEA project.
Also, I'm just curious, does Eclipse handle the multiple VSS correctly? If so, can you explain how it does so?
-Alex
To clarify: if I create one IDEA project per VSS project, it still doesn't work. I did check that, and obviously the code doesn't compile (due to dependencies), but even just considering them as files, the VSS integration still fails.
Eclipse does handle this correctly. There are many drawbacks in Eclipse as far as I'm concerned, but that is one feature that works correctly. And as the team I'm working with are happy with Eclipse and VSS, there's little I can do to encourage them to switch to IDEA (or even just use it efficiently by myself) if this doesn't work. I can't explain how it works, but it does!
The plug-in is named "VSS Plugin version 1.6.1 for Eclipse 3.1" and is available from http://sourceforge.net/projects/vssplugin/ ; it only allows one VSS database per project, but as Eclipse lists all projects in the same workspace in the explorer on the left (by default), it's easy to navigate between projects and resolve dependencies. This is why (to keep the same behavior) I'm trying to load these different codebases as IDEA modules (to have them handy at the same time and to resolve source-code-level dependencies). Like I said however, it doesn't seem to help from a VSS viewpoint if I use one IDEA project per VSS project.
- Chris
Hello Christopher,
Yes, this is very helpful. We are working on this issue.
Thanks,
Vladislav Kaznacheev
Project Manager, IntelliJ IDEA
http://www.jetbrains.com
"Develop with Pleasure!"