File status in Eclipse Plugin

[B.fernandez]

Hello,

We are looking for a VSS alternative and we are doing some tests with the Vault Standard trial version in order to replicate our current way of working. We are using the last Vault version and Eclipse 3.7, and lock-modify.unlock.

Some of the problems we have found:

- If we check out a file, the status does not change on the eclipse navigator. We have to do a manual refresh (f5, sometimes several times) to see the icon change. The same with the rest of the file states. I don't know when and why the icon status refreshes.
- The eclipse plugin do not show if a file is checked out by another user.

Is this a problem in our configuration, a known bug or it's the expected behaviour?

Also, we forced the check out to edit a file, but if the file is already checked out by another user, you can still edit it (you can see a exclusive-lock message). We have set that the files, if they are not checked out, should be read only. It's not a huge problem, but we would like to prevent it or do it more difficult for the user.

Could the Vault Professional eclipse plugin (obviously running against a Vault Professional server) solve some of this problems? Does it have more configuration options or works different in some way?

Thank you very much.

[lbauer]

- If we check out a file, the status does not change on the eclipse navigator. We have to do a manual refresh (f5, sometimes several times) to see the icon change. The same with the rest of the file states. I don't know when and why the icon status refreshes.

I was able to reproduce this, but I'm not sure if this is intended behavior.

If you just start editing the file and save it, it will be automatically checked out.

I need to do some more investigation on this.

- The eclipse plugin do not show if a file is checked out by another user.

This is expected behavior. The Eclipse plugin does not show checkouts from other users.

Also, we forced the check out to edit a file, but if the file is already checked out by another user, you can still edit it (you can see a exclusive-lock message). We have set that the files, if they are not checked out, should be read only. It's not a huge problem, but we would like to prevent it or do it more difficult for the user.

If a file is exclusively locked, another user should not be able to check it out. A user is not prevented from changing the read-only status of a file on disk, and editing it. Could you provide more details on what you mean by "we forced the check out to edit a file" ?

Could the Vault Professional eclipse plugin (obviously running against a Vault Professional server) solve some of this problems? Does it have more configuration options or works different in some way?

Vault Professional has the same Eclipse functionality. The difference between Vault Standard and Vault Pro is that Vault Pro has work item tracking.

[B.fernandez]

Hi,

About this:

Also, we forced the check out to edit a file, but if the file is already checked out by another user, you can still edit it (you can see a exclusive-lock message). We have set that the files, if they are not checked out, should be read only. It's not a huge problem, but we would like to prevent it or do it more difficult for the user.

If a file is exclusively locked, another user should not be able to check it out. A user is not prevented from changing the read-only status of a file on disk, and editing it. Could you provide more details on what you mean by "we forced the check out to edit a file" ?

The thing is, if UserA checks out a file and UserB tries to edit the same file, he will get an error saying that he cannot check out the file. Nevertheless, he can still edit it and work with an "out of date" copy.

[lbauer]

Does Vault make the file writable on disk or does the user make it writeable to edit?