Bug 233669 - [validation] flag imported x-internal packages as discouraged access in manifest editor
Summary: [validation] flag imported x-internal packages as discouraged access in manif...
Status: RESOLVED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: bugday
Depends on:
Blocks:
 
Reported: 2008-05-23 09:53 EDT by Thomas Watson CLA
Modified: 2019-09-09 09:06 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Watson CLA 2008-05-23 09:53:56 EDT 
See bug 233668

In the project org.eclipse.equinox.p2.core the packages org.eclipse.core.runtime.adaptor and org.eclipse.osgi.internal.resolver are not getting flagged as warning for discouraged access

Note that the access rules on the PDE classpath container *do* correctly place the discouraged access rules, but the bundle manifest does not show a warning.
Comment 1 Chris Aniszczyk CLA 2008-05-23 10:02:07 EDT 
How about that... I am able to reproduce.
Comment 2 Chris Aniszczyk CLA 2008-05-23 11:55:46 EDT 
This is an enhancement request. PDE's BunderErrorReporter currently doesn't flag imported packages that are internal as discouraged. PDE does setup the access rules properly so JDT should be reporting the discouraged access in the Java file, if not, please file a bug against JDT because the access rules look correct.
Comment 3 Chris Aniszczyk CLA 2008-05-23 11:56:39 EDT 
btw, this is somewhat closely related to bug 208972 where we wanted to decorate imported packages that come from internal or x-friends.
Comment 4 Thomas Watson CLA 2008-05-23 12:09:43 EDT 
Hmmm, ok.  I really thought we used to flag these kinds of access rules in the manifest, oh well.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:17:01 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 6 Julian Honnen CLA 2019-09-09 02:23:07 EDT 
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
Comment 7 Thomas Watson CLA 2019-09-09 09:06:13 EDT 
Not a high priority at this point.  Looks like wontfix.