Bug 189155 - Better message for access restrictions.
Summary: Better message for access restrictions.
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: polish
Depends on:
Blocks:
 
Reported: 2007-05-25 11:15 EDT by Jeff McAffer CLA
Modified: 2011-03-29 09:14 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff McAffer CLA 2007-05-25 11:15:31 EDT
When someone accesses a type that they are no allowed to because of an access restriction they get a message somehting like

Access restriction: The method setDefaultMaxConnectionsPerHost(int) from
  the type HttpConnectionManagerParams is not accessible due to  
restriction
  on required library org.apache.commons.httpclient-3.1

It would be good if the message said what package the type was in.  That way the would know more directly what they have to do to get proper access (e.g., get the provider to export it, whatever...
Comment 1 Wassim Melhem CLA 2007-05-26 17:14:28 EDT
These messages are coming from the compiler of course.
Comment 2 Philipe Mulet CLA 2007-05-28 09:20:00 EDT
All compiler error messages are shortened. All qualified information is however available in the marker. Maybe hover could reveal it ?
Comment 3 Jeff McAffer CLA 2007-05-28 09:46:12 EDT
that seems like a reasonable start.
Comment 4 Philipe Mulet CLA 2007-05-29 05:21:38 EDT
Or if this is the only message causing grief (which I suppose it is), then we could improve it to reveal the package.

Access restriction: The method setDefaultMaxConnectionsPerHost(int) from
  the type HttpConnectionManagerParams is not accessible due to  
restriction on package x.y.z in required library org.apache.commons.httpclient-3.1

i.e. we could make access rules carry more context information (currently any type may carry a restriction, and in manifests there is more of a package level granularity). I think our support can allow 3rd parties (contributing the access rules) to provide more context.