starting over with Eclipse

[Don Robinson]

I'm just getting started with Eclipse (3.4.2) and am a regular user of Vault (4.1.4.18402) with MS Dev Studio 2005. I downloaded the plugin (4.1.4.18429) and it seems to have installed fine. Somewhere along the way (setting up a sandbox folder in the repository or ?) I screwed things up, and I'd like to wipe out and start over. I can wipe on the repository side, but Eclipse seems to persistently know about Vault, and I can't make it forget. (This isn't supposed to sound like a Country & Western song!) On the Eclipse side, how do I remove all traces of the Vault connection, so I can start over?

[Don Robinson]

After some fooling about I manged this myself. In Eclipse, I deleted the Project (which is only a sandbox, thankfully) and re-created it, which includes pointing to the files on my workstation. After that, I reconnected to Vault at the Project level (R-click at Project level > Team), I only created the Sandbox-level folder through the Vault UI, and I let the Eclipse plugin create the project folder beneath it. I then added the 2 toy files I am most interested in putting under source control. Problem seems to be solved.

[Beth]

Thanks for the update. I'm happy to hear you are working again.

[Don Robinson]

After closing down yesterday (with 2 toy files checked out), I restarted today, unsuccessfully. I restarted Eclipse and Vault integration also started up automatically: (1) password prompt; (2) Connecting to Vault Server; (3) Loading the name repository; (4) Refreshing. No errors reported. But the 2 files don't show as checked out, and when I look at the properties (r-Click, Vault Properties) the message reads:

Could not map path to anything useful: E:\Documents and Setting\Don\My Documents\Spotfire S+\Project1\Explore Eigen\MyTestFunc.ssc

If I select one of my toy files and r-Click > Team > Add, I get an error message

"The command [AutoAddCommand] failed" (Object reference not set to an instance of an object.)

Any suggestions? Where to look? What to try?

[shannon]

Are you on Windows or some other platform?

Can you check your Eclipse error log: Window->Show View->Error Log
and also %temp%/VaultEclipseLog.log for any errors?

[Don Robinson]

Running - WinXP Pro SP3
I don't show this menu option (Window->Show View->Error Log); only Window > Show View. Not sure why it is absent!
I am attaching the log you mention. I don't have the under-the-hood necessary to see what is significantly wrong.

[shannon]

Your Eclipse install is probably just a different flavor than mine...the viewer is just a convenience anyway.

You can probably find the Eclipse log on disk in your workspace. Something like this: <workspace>\.metadata\.log

[Don Robinson]

Here is a zipfile with the 2 logs. Thanks for your help - it is really appreciated

[shannon]

Are you actually using Eclipse or is this an Eclipse-based ide? I'm seeing a lot of references (and errors) to packages that start this way: com.insightful.splus?

[Don Robinson]

That's right - sorry if I didn't appreciate the distinction between them, and its possible imporance... this is all new to me. The IDE is the "TIBCO Spotfire S+ Workbench" a statistical computing environment that was originally developed as S-Plus by Insightful (and aeons ago, developed by Bell Labs), before linking to Eclipse. A nearly parallel open source version of the software is called "R". The company has changed hands, but I guess the package references haven't. Do you think those errors are the root of the problem I am having? Any advice at this point?

[shannon]

It's no problem, most people don't think to mention it but you're right, it can be important. Sometimes Eclipse-based IDEs are missing packages that we depend on.

I don't think those errors are the root of your problem, but I can't be sure some of them aren't related yet.

Do you have the GUI client installed? I'd like you to find whatever Vault file relates to this path that you got the error message for: E:\Documents and Setting\Don\My Documents\Spotfire S+\Project1\Explore Eigen\MyTestFunc.ssc

Does the working folder seem right for that file in the GUI client?

[Don Robinson]

I have the Vault Client (4.1.4.18402). The working folder looks correct: i.e., the ssc file [which is simple text] exists at E:\Documents...

(One thing that I wondered about - but which I think is correct - is that I tried changing the name of the Vault folder from FVS\S Sandbox\... to FVS\S-Sandbox\ and then finally just settled on \FVS\Sandbox at the end of yesterday's experimenation. This is the current folder name.)

[shannon]

I actually wanted to know if that was the working folder the GUI client is showing for that file, not just that it exists. If you look at that file in the GUI client, is that the working folder that is displayed?

Is the Sandbox folder mapped to your project in Eclipse? If it's above or below the project level it shouldn't be a problem, but if that is your eclipse "project" then renaming it probably caused some chaos.

[Don Robinson]

OK - yes - the GUI shows the same working folder as Eclipse. Looked at from each Interface: Vault and Eclipse, both show the same directory on my workstation. As an indirect confirmation, I can check out the files in Vault, and while they are not marked as such in Eclipse, they can be saved (i.e. are not read-only) at that point, whereas when they are checked in, they cannot be saved via Eclipse.

At this point I'd like to try wiping and starting over. What I'd like to know is: what do I need to do to create a clean slate? What files/directories are going to be persistent? If I go this route, should I start a completely new repository to be guaranteed a clean start?

Thanks for all your help

[shannon]

A checkout from Vault and a checkout from Eclipse may show up a little differently. So if you want to edit in Eclipse, you should checkout from Eclipse, not the GUI client.

My next suggestion was going to be to start over If you can, it would be easiest just start a new workspace (in Eclipse for me, I'd do this by File->Switch Workspace). Then import whatever project you need from Vault to the new workspace. You don't need to wipe your Vault repository, the Vault ties in Eclipse are workspace/project related, but all stored by the Eclipse workspace.