Bug 336037 - [build path] Give better hints when a class path container does not allow modifications
Summary: [build path] Give better hints when a class path container does not allow mod...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2011-02-02 01:21 EST by Ed Willink CLA
Modified: 2011-02-03 13:28 EST (History)
2 users (show)

See Also:


Attachments
Show current location path on properties pages (18.28 KB, patch)
2011-02-03 13:25 EST, Markus Keller CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2011-02-02 01:21:19 EST
Trying to debug missing source attachment in M5 for EMF.

The Property Page of the plugin in the Plugin-Dependency in the Package Explorer is unhelpful.

Firstly it reports: The current class path entry ... which does not allow modification ...

This may be true, but it could at least identify when the unmodifiable setting is.

Secondly: it could describe/link to where a modification could be made.

Please be as helpful as possible to those debigging classpath nightmares.
Comment 1 Dani Megert CLA 2011-02-02 03:14:04 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.
Comment 2 Markus Keller CLA 2011-02-03 13:25:32 EST
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.
Comment 3 Markus Keller CLA 2011-02-03 13:28:18 EST
(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.