Summary: | [build path] Give better hints when a class path container does not allow modifications | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Ed Willink <ed> | ||||
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> | ||||
Status: | ASSIGNED --- | QA Contact: | |||||
Severity: | enhancement | ||||||
Priority: | P5 | CC: | daniel_megert, markus.kell.r | ||||
Version: | 3.7 | Keywords: | api | ||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Ed Willink
2011-02-02 01:21:19 EST
> This may be true, but it could at least identify when the unmodifiable setting > is. Did you mean: identify *where* the unmodifiable setting is? > Secondly: it could describe/link to where a modification could be made. Well, as it says: user modifications are not allowed ;-) However, we could try to tell you which source bundles are missing in your install. For that we would need API to get more details from the container. This not only affects source attachments but also other properties like native libraries. Created attachment 188262 [details]
Show current location path on properties pages
Showing the current location path is easy to do and doesn't need callbacks to the classpath container implementer.
(In reply to comment #2) > Created attachment 188262 [details] [diff] > Show current location path on properties pages Committed to HEAD. BTW: The current values are already visible in project properties > Java Build Path > Libraries > Plug-in Dependencies > expand plug-in node. |