Eclipse plug-in 4.0.4 - File changed on the file system ...

shannon · Post by **shannon** » Mon Nov 19, 2007 11:09 am

Just to be sure: did you try restarting eclipse after you made the settings changes? And also, you made the settings changes in Eclipse under Preferences (not in the GUI client)?

Post by **jclausius** » Mon Nov 19, 2007 11:35 am

StuartHemming wrote:FWIW these are exactly the options I have set in Vault here and VS still notices that the file has changed after I commit the file to the repository.

Stuart, there are really two different threads going on here one for Eclipse and one for Visual Studio. The suggestion I posted was for Keygene and Eclipse.

Stuart, when you commit, are you using Visual Studio to commit the files or are they being committed another way (Vault GUI or command line)?

Keygene · Post by **Keygene** » Tue Nov 20, 2007 3:53 am

shannon wrote:Just to be sure: did you try restarting eclipse after you made the settings changes? And also, you made the settings changes in Eclipse under Preferences (not in the GUI client)?

Yes and yes ...

StuartHemming · Post by **StuartHemming** » Tue Nov 20, 2007 4:01 am

jclausius wrote:Stuart, there are really two different threads going on here one for Eclipse and one for Visual Studio. The suggestion I posted was for Keygene and Eclipse.

I know, but when I hijack a thread, the stays hijacked!

jclausius wrote: Stuart, when you commit, are you using Visual Studio to commit the files or are they being committed another way (Vault GUI or command line)?

Via the Vault GUI.

I only butted in (again) 'cos you'd suggested something new. All I really wanted to do was highlight that it's prolly not just an Eclipse problem.

Post by **jclausius** » Tue Nov 20, 2007 8:19 am

StuartHemming wrote:Via the Vault GUI.

That would explain things.

When using any of the Visual Studio IDE clients, unless you commit from within the IDE, you will be prompted to reload the file because the client libraries outside the Visual Studio process will be touching the files causing a reload. Try committing Vault's Change Set from within Visual Studio.

StuartHemming · Post by **StuartHemming** » Tue Nov 20, 2007 8:26 am

No can do. Can't use the VS addin as almost all of my work is on web sites. See previous messages for details.

Post by **jclausius** » Tue Nov 20, 2007 8:55 am

StuartHemming wrote:No can do. Can't use the VS addin as almost all of my work is on web sites. See previous messages for details.

I'm jumping in the thread mid-stream, but I thought you were talking about using the Vault IDE client within Visual Studio, and Visual Studio was prompting you to re-load the files upon a commit. A bit similar to this thread about using the Eclipse plugin and seeing the same results.

Are you saying you're using the Vault GUI client and Visual Studio is prompting you about reloading open files?

StuartHemming · Post by **StuartHemming** » Tue Nov 20, 2007 9:01 am

jclausius wrote: Are you saying you're using the Vault GUI client and Visual Studio is prompting you about reloading open files?

Yep. That's exactly what I'm saying.

Post by **jclausius** » Tue Nov 20, 2007 9:05 am

OK. That is not unexpected behavior. Especially if the file is old and the Vault client does a merge before you commit any changes. If the file is *not* reloaded within VS, you may end up losing changes from other users.

Tell you what. Let's start a new topic regarding the issues with Visual Studio. The problem you're describing has nothing to do with this thread which was causing some confusion about what is happening.

StuartHemming · Post by **StuartHemming** » Tue Nov 20, 2007 9:10 am

Fair enough