Summary: | inaccurate error message when dependent project is closed | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | John Arthorne <john.arthorne> |
Component: | Core | Assignee: | Kent Johnson <kent_johnson> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P1 | CC: | knut_radloff |
Version: | 2.0 | ||
Target Milestone: | 2.0 M3 | ||
Hardware: | PC | ||
OS: | Windows NT | ||
Whiteboard: |
Description
John Arthorne
2002-01-23 17:33:34 EST
JavaProject.getExpandedClasspath should handle a closed project the same as a missing project by reporting a missing warning. The build would continue without any dependency on the missing project. A closed project isn't really 'missing', but this is interesting. The problem is that the classpath will keep surfacing it, so #getExpandedClasspath will still answer some closed projects (classpath entries are simply handles to project). These must be filtered out by client code if unable to accept them. I added a notification when a required project is closed, however the builder error message should be better nuanced to accomodate with classpath issues. Why does it produce the error: build.incompleteClassPath = The project was not built since its classpath is incomplete. Fix the classpath then rebuild it Closed projects are now treated the same as missing projects... a warning is issued & the build proceeds. If no references exist to the closed/missing project, the build is error free. |