Summary: | Move a Java file, errors remain | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jed Anderson <jed.anderson> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | rich |
Version: | 2.0 | ||
Target Milestone: | 2.1 M1 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: | |||
Bug Depends on: | 2857 | ||
Bug Blocks: |
Description
Jed Anderson
2002-04-08 11:58:33 EDT
Markers are attached to a resource and move with the resource. When the file is moved out of the class path then the problem markers should be removed. Moving to JDT CORE for comment. We are addressing the case where a JAVA file becomes a non-java one (see bug 2857). And this scenario is very similar to the other issue. Now we cannot easily get rid of markers in the JavaModel update, since this one is implemented in term of POST_CHANGE event, where the resource tree is locked. Post 2.0, we might want to revisit this and move the JavaModel update onto the PRE/POST_AUTO_BUILD change notification. Will reconsider post 2.0 *** Bug 14193 has been marked as a duplicate of this bug. *** Reopening Clearing resolution |