Summary: | validateEdit not called when changing .classpath | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Josh Heidebrecht <jheidebr> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0.1 | ||
Target Milestone: | 2.1 M3 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Josh Heidebrecht
2002-09-23 13:18:21 EDT
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. |