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

StuartHemming · Post by **StuartHemming** » Wed Nov 14, 2007 9:22 am

Have I missed something here in your explanation?

I edit something in VS, save and compile. Assuming my changes are complete I go to Vault, commit my changes and go back to VS to get on with item 2,334,123 on today's list and when VS becomes the active app it tells me that the file has changed and asks if I want to reload it.

I've learned that the answer to this question is "No" 'cos if I answer "Yes" Vault takes it into its head that the file has changed again* and puts it in my PCS.

* I think this is 'cos VS marks the file as dirty and requiring a save. I could be wrong mind.

Beth · Post by **Beth** » Wed Nov 14, 2007 10:06 am

The one change that does happen is that the file gets marked as read-only after check in.

I think that could be fixed by using CVS mode in this case, or go into the Vault options and set it that all files should not be marked as read-only. I think CVS mode would be better. You then don't have to check things out, but after you edit them, they will just show up as edited in Vault.

To set CVS mode, go to Tools - Options - Concurrent Development and click the CVS button.

StuartHemming · Post by **StuartHemming** » Wed Nov 14, 2007 10:13 am

I am using CVS, that's why I said I committed my changes rather than said checked in. We have the option set to alway leave the file checked out.

Beth · Post by **Beth** » Wed Nov 14, 2007 12:26 pm

Do you close the file before checking it in?
Are you sure you are getting it saved to disk before checking in?

It could be a case of where VS is seeing Vault is making a timestamp change when it gets checked in. In fact, that's probably what is going on here.

Also, if you use keyword expansion, that causes Vault to make a change to the file on checkin.

StuartHemming · Post by **StuartHemming** » Wed Nov 14, 2007 12:41 pm

Do you close the file before checking it in?

Nope.

Are you sure you are getting it saved to disk before checking in?

Yep.

Also, if you use keyword expansion, that causes Vault to make a change to the file on checkin.

Not doing that though.

Beth · Post by **Beth** » Wed Nov 14, 2007 1:09 pm

In that case I think it's the time stamp that VS could be seeing. Vault does "touch" the file when it checks in, and with file open, VS probably sees the change and then thinks the file you have open is not up to date with what's on the disk.

StuartHemming · Post by **StuartHemming** » Wed Nov 14, 2007 1:31 pm

Fairy snuff.

I'll just continue saying "No" then.

Keygene · Post by **Keygene** » Thu Nov 15, 2007 9:23 am

To come back on the initial topic ...

Beth wrote:Do you have auto commit turned on? Try turning that off.

This was seen back in 4.0 with the VSIP interface but hadn't yet been reported in Eclipse as far as I can tell.

After trying the first suggestion, if it persists, try going to the 4.0.5 Eclipse plug in so you are working from the version that matches your Vault client.

I updated the plugin to 4.0.5 and did turn off auto commit and nothing changed.
I haven't tested the thing about keyword extension as I 'm not the admin of the vault server.
However, this is the default installation, just for testing purpose, so are java files turned on for keyword extension in the default installation ?

Beth · Post by **Beth** » Thu Nov 15, 2007 11:27 am

Keyword expansion is not turned on by default. I think Shannon gave the answer for your question with Eclipse. She was 2 posts after my first response, and she knows much, much more about Eclipse.

Keygene · Post by **Keygene** » Fri Nov 16, 2007 3:22 am

Beth wrote:Keyword expansion is not turned on by default. I think Shannon gave the answer for your question with Eclipse. She was 2 posts after my first response, and she knows much, much more about Eclipse.

OK thanks ...
I think that discards a regular use of Sourcegear for Java development with Eclipse then

Beth · Post by **Beth** » Fri Nov 16, 2007 4:09 pm

I guess don't see how that could be. It's the same for all SCC providers. I can see that it's an annoyance, but it makes sense why Eclipse and VS do that. If they didn't, a user could potentially lose their changes. They just aren't discriminate about where the changes come from.

If you know of some other SCC software that works differently, send me an email at support at sourcegear.com (attn: Beth), with a link to this thread so I remember what we were talking about and I'll check it out when I can.

Keygene · Post by **Keygene** » Mon Nov 19, 2007 8:53 am

I was not aware it was related to Microsoft specific API, but in comparison to CVS or SVN which are potential other solutions for our needs (at least for Java development), that makes a difference.

Post by **jclausius** » Mon Nov 19, 2007 10:03 am

Keygene:

I thought about this problem some more over the weekend. Can I ask you to try some new settings?

I'm wondering if we can configure your Eclipse plugin to leave the working folder copy in its original state, causing Eclipse to not re-load.

Set the check in times to use the "Modification" setting and also set the GET attributes to be "make-writable" as well as *not* set the Check Out before Check In option. You'll also need to remove any read-only file attributes on files you already retrieved from Vault. You could also do this by issuing a GET from Vault with this GET option set.

The goal is to minimize Vault's impact on the file in the working folder to see if that will make Eclipse happy.

StuartHemming · Post by **StuartHemming** » Mon Nov 19, 2007 10:11 am

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.

Keygene · Post by **Keygene** » Mon Nov 19, 2007 10:58 am

jclausius wrote:Keygene:

I thought about this problem some more over the weekend. Can I ask you to try some new settings?

I'm wondering if we can configure your Eclipse plugin to leave the working folder copy in its original state, causing Eclipse to not re-load.

Set the check in times to use the "Modification" setting and also set the GET attributes to be "make-writable" as well as *not* set the Check Out before Check In option. You'll also need to remove any read-only file attributes on files you already retrieved from Vault. You could also do this by issuing a GET from Vault with this GET option set.

The goal is to minimize Vault's impact on the file in the working folder to see if that will make Eclipse happy.

Hi,

thanks for your help, but unfortunately, there is still this pop-up message