Summary: | Markers for build path not updated on (re-) build (1GJY69S) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> |
Component: | Core | Assignee: | Kent Johnson <kent_johnson> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P2 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 M2 | ||
Hardware: | All | ||
OS: | Windows NT | ||
Whiteboard: |
Description
Dani Megert
2001-10-10 22:54:01 EDT
PRODUCT VERSION: 0.135 A full build would be a good opportunity to refresh the buildpath markers. Look at JavaProject.getResolvedClasspath implementations, one allows to tell whether we want to refresh the markers, it should be used when doing a full build (when the classpath changes, it will also cause a full build). Changed JavaProject.getExpandedClasspath(boolean, boolean) to flush the old markers & recompute the new ones, and also changed the NameEnvironment to ask the JavaProject to generate the problem markers. |