Community
Participate
Working Groups
The .classpath is under source control and is checked in. From the 'Java Build Path' properties dialog for the project I am trying to change a classpath variable name from XXX to YYY. When I complete the change and choose Ok I receive and error stating that the file could not be checked out. I have validateEdit processing turned on, but the SCM provider is set to ignore validateSave requests.
That clearly would break all tooling expecting to modify resources with using editor interaction (validateEdit is meant to be used by editors). Pretty much all programmatical change to a resource would run into the same issue. The SCM provider settings seems to imply that the behavior you are observing is the right one. Only files which you deliberately edited are to be checked out.
It appears that we would need to be calling #validateEdit on each resource modified in a headless way, like in your scenario. Planned for fix for 2.1M2
Deferred to M3.
Fixed (in JavaProject#setSharedProperty).
Verified.
I marked this bug as verified by error.
Marked as resolved.
The fix is released but i can not verify if the fix work. Josh - could you verify if the bug is corrected in the last integration build.
Working in M3. fyi You can use the pessimistic provider (see the Team team) to emulate a ClearCase like SCM.