Summary: | SEVERE: Not all external JARs show up in packages view (1GD0JZO) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | John Arthorne <john.arthorne> |
Component: | Core | Assignee: | David Audel <david_audel> |
Status: | VERIFIED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 F2 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
John Arthorne
2001-10-10 22:52:03 EDT
PRODUCT VERSION: 0.101 selfhost There should not be any root for missing elements, this is now enforced. Some classpath entries would not be mapped to any roots. The remaining question is: when is it a good time to refresh the roots ? On a full build ? I would rather vote for a forced manual refresh, however there is no way to hook into this action. Please check behavior with latest. Behavior is still the same. I still have no idea how to solve this without a notification from core. Will review after 2.0 if core provides us with some support. JAR refresh mechanism got added (using explicit user action). Fixed. Closed Verified. Verified. |