I'm pretty sure that SJ Eclipse already handles this just fine. You can set up different projects
to point to different spaces in a single archive, different archives on the same server, or
different archives on different servers. When you switch from a project on one archive to a
project on another archive, the only way you'll be able to tell is that SJ Eclipse will prompt you
again for your login info. (In fact, I've just tested and this is exactly what happens.)
This is a bit of a pain, but even this can be worked around.
The SJ client deals with this by first trying to log in to the new archive using the user's
current login info. If that works, presto. If it doesn't, SJ catches the exception and then
prompts with the login dialog.
Something like that will probably work in SJ Eclipse.
> I am trying to add multiple project support to the sourcejammer eclipse plugin (V 2).
> Say I have 3 projects in the workspace.
> So SJ connection properties ect. can all be set for all 3 of them separately.
> When Eclipse starts, it can connect to the SJ archive for each project in the workspace (if
> Files/folders can be operated on transparent to the user that 3 connections to the SJ server are
> running in the background.
> However, both SimpleInterface and CommandCentral and singletons.
> So at one time, the plugin can only hold one instance of each, and so only one connection to
> only one archive on the server.
> Any ideas to get around this problem (without changing the SJ code)???
> Karan Gupta
> Software Engineer
> TransCore, San Diego
> (858) 736 - 8246
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around