starting over with Eclipse

[Don Robinson]

I created a brand new Eclipse project and was able to add the .project and 2 files to the Vault repository. The working folders seem fine to me (see attachment for screen cap). The comment I added when I first commited the files is visible through the Vault UI, so I am confident that this step happened properly. When I shut down the Eclipse platform and restarted, the files are not recognized as under source control, even though I go through the login steps without any warnings or errors being apparent. The files cannot be re-added (as in my 4th posting on this thread from 11:16 on May 8th).

I am tending to the view that there may be a version compatibility issue with the Vault plugin 4.14.18429 (which is compliant with Eclipse 3.2), and the Eclipse platform 3.4.2.M20090211-1700.

For your reading pleasure (:? ) I am enclosing a zipfile with a screen cap, and the .metadata/.log file, which has what look to me to be fault handling interchanges between sourcegear plugins and the eclipse internals. (I annotated the .log file a bit) I don't know how much more of this I can take!

[shannon]

The error you've marked as happening during the properties check is happening when you right-click. I know what this is and it tells me that your IDE is missing a package that normally comes with Eclipse. However, it handles a very small piece of functionality and I've seen people work with this error before. (It allows us to test if you're connected before we show the team menu and if you aren't, show a login command there.) This is not causing your problem.

The error you've marked as occuring on shutdown isn't being thrown by our plugin. It looks like the ide is trying to display something to you in the console, but the console has already been disposed...unfortunately, I can't tell anything more than that from the log.

We've tested with 3.4.2 before, but I've just run another test with the exact same plugin version you're using to be sure. I'm not seeing the same problems you are.

There are 2 more things I can think to check:
1. Do you have access to your server log? It would be on the server machine here: C:\WINDOWS\Temp\sgvault\sgvault.log
2. You could download regular Eclipse 3.4.2 (http://www.eclipse.org/downloads/downlo ... -win32.zip) and try your test. If you don't have problems, then it's something specific to the Spotfire IDE.

Edit: I've just thought of something else. Are you using the default cache location or something else? Look at your options in both Vault and Eclipse, do the cache locations match?

[shannon]

I think that's it. If I set up Eclipse and import a project and then change my cache location, when I restart Eclipse I'm seeing the behavior you are.

[Don Robinson]

Thanks for your insight on the error I mentioned in the .log file. Your explanation makes sense.

Good clues for the cache issue. I haven't changed my cache location in at least a year... but if the Spotfire IDE
expects it to be done a certain way, that could be it.

Attached is a screen cap of my cache in its current state (i.e. its state throughout this issue up until today). I think this is what you must be referring to? I'll try changing and see what happens.

[shannon]

Just make sure the cache options match in Spotfire and the Vault GUI client. There are options that can't be shared between the two because the GUI client makes use of the registry and that doesn't make sense in a cross-platform app like Eclipse.

[Don Robinson]

You were right about the cache location. The Vault plugin to Eclipse was set to "In Client Cache Folder", while my Vault UI was set to "In Working Folders." So I tried to make them the same ("In Working Folders"), but on the Eclipse side I couldn't get the setting to persist between shutdowns of the Spotfire IDE. Since it looked like it would only accept "In Client Cache Folder" I changed my Vault UI side to make them agree, and set up a new clean project.

Everything seemed to go OK initially. Working folders agreed, the plugin features worked (e.g. Check in, Check out), which agreed with the state as seen through the Vault UI. In particular, when I r-clicked and inspected the Properties of the script files, there was sensible information from Vault, and not the "Could not map path to anything useful..."

But when I shut down the Spotfire IDE, and restart, the problem is still there once I start up again.

We should rename this thread "Two steps forward, one step back!" It looks like the root of the problem is in some error in where information is stored between sessions.

Should I try changing (in both Vault UI and Eclipse) the Store Client Cache Folder from their current location: "In User Local Settings Folder" to "In Custom Folder", making sure they are the same folder?

[shannon]

So, just to be clear....you changed a cache setting in the Vault Eclipse preferences and when you restarted it had reverted?

I'm sorry, I know this is frustrating, but this is extremely weird, bear with me

I'm going to try going about this a little differently....Can I see a copy of this file: E:\DOCUMENTS AND SETTINGS\DON\MY DOCUMENTS\SPOTFIRE S+\PROJECT1\.Data\__bdo\imwork\Local Settings\Application Data\Sourcegear\Client\settings.xml (if it exists) And also a screenshot of the Eclipse preferences page with the cache settings on it.

[Don Robinson]

That's correct: it reverted.

I made a copy of the two settings.xml files (attached, renamed), and a screen cap from Eclipse UI. I don't see any syntax problems with the tags, per se.

When I open Explorer to see what is going on with file/directory creation, I see this: when I choose WF (Working Folders) in the Eclipse UI, the XML file has this tag (<StoreDataInWorkingFolders>True</StoreDataInWorkingFolders>). I exit from Eclipse and the XML file remains the same. I restart and refresh the file/directory view in Explorer, at the time the UI is paused asking for my Vault login password. The /Local Settings folder (and of course, the XML file) has been removed. I provide my password and during the refresh with the Vault database, the Application Data/Sourcegear/Client folder is recreated and a new settings.xml file is created with this tag: <StoreDataInWorkingFolders>False</StoreDataInWorkingFolders>. Inspecting the properties after the login is complete, the CCF (Client Cache Folder) is selected. That looks interesting and unexpected.

Keeping the CCF setting, I exit Eclipse and a new piece of folder tree is created:

E:\Documents and Settings\Don\My Documents\Spotfire S+\Project4\.Data\__bdo\imwork\Local Settings\Application Data\Sourcegear\Vault_1\Client\50158EE2-B0D9-4755-AF5E-2ABBCC25915F

I exit Eclipse and relaunch. During the pause-for-password, I note that the /Local Settings folder (and all the tree just created) is again deleted. A new bit of tree is created: /Local Settings/Application Data/Sourcegear/Client, with a fresh settings.xml file (with the WF tag FALSE). Keeping the CCF setting I exit Eclipse again and the same new folder (/Vault_1/...) is created (see above). Restarting is the same: the /Local Settings folder is gone, only to be recreated during the connection. This seems repeatable, and it looks like it might remove all the state information from the prior session.

I've been describing manipulation of the "Store Working Folder State/Baseline Files" only. Is "Store Client Cache Folder" involved too?

[shannon]

Thanks for the extra legwork, that's all helpful information. That's not the normal location for your local settings directory, so the question is, have you changed it or is it possible that Spotfire is doing it for you and then cleaning up after itself on launch? Can you load up some project in Spotfire that isn't bound to Vault and watch what happens to the Local Settings directory?

The default path is something like C:\Documents and Settings\<username>\Local Settings\Application Data where this part: C:\Documents and Settings\<username>\ is defined by the USERPROFILE environment variable.

[Don Robinson]

I also found it interesting that it would make this directory. I do, in fact, have a parallel directory in the default location, all the way down the same GUID:

C:\Documents and Settings\Don\Local Settings\Application Data\SourceGear\Vault_1\Client\50158EE2-B0D9-4755-AF5E-2ABBCC25915F\DonRobinson

This default location is used by all my other Vault-related projects, as far as I can tell. I will try creating a project and leave Vault out for the moment. More on that later.

A suggestion - would you be interested in working on this over the phone. I wonder if we might make faster progress. You could email me a phone # to drobinson at essa dot com. We could also use a GoTo link, which would be a bit more dynamic.

[shannon]

Yeah, the one in the default location is the one the GUI client is using. And the one Eclipse would be using normally.

You might want to poke around in the Spotfire settings...maybe you'll find a setting related to that location.

I've emailed you a number to reach me with.

[Don Robinson]

TIBCO Spotfire tech support was able to locate the problem and provide a workaround. Although it is very specific to their plug-in, I am posting it here for posterity:

====================
From the Workbench main menu choose Window, Preferences. In the Preferences dialog click Spotfire S+ in the left pane. In the right pane remove the text:

library(bigdata, first=T)

…and replace it with the code:

.JavaMethod("java/lang/System", "setProperty", "(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;", "user.home", getenv("USERPROFILE"))

Then click Apply.
====================

After doing this, the Vault state is correctly remembered between Eclipse sessions.

[lbauer]

Thanks for the update, and for posting the information.