Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 354916

Summary:

Invalid discouraged access in plugin.xml (access rule configured!)

Product:

[Eclipse Project] PDE

Reporter:

Timotei D <kimi_anwen>

Component:

Assignee:

PDE-UI-Inbox <pde-ui-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

curtis.windatt.public, remy.suen

Version:

3.7

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

stalebug

Attachments:

Description	Flags
The classpath file	none

Description Timotei D

2011-08-17 04:26:15 EDT

Build Identifier: 20110615-0604

I get 'Access to referenced class 'org.eclipse.xtext.builder.nature.ToggleXtextNatureAction' in attribute 'class' is discouraged' in my plugin.xml, EVEN if I've configured the access rules.
This is how the classpath for that project looks like the attached file.

The problem is, in the .java files the warning is not triggered, only in the plugin.xml.

Reproducible: Always

Comment 1 Timotei D

2011-08-17 04:26:38 EDT

Created attachment 201627 [details]
The classpath file

Comment 2 Timotei D

2011-08-17 04:27:22 EDT

Hmm.. It should be eclipse indigo. 3.7

Comment 3 Curtis Windatt

2011-08-31 15:08:28 EDT

Can you provide more detailed steps?  When I add an access rule to the PDE container, I get warnings on any java file using packages that match that access rule.

Comment 4 Timotei D

2011-08-31 16:02:17 EDT

I have my plugin project:

1) Right click on it
2) Build Path -> Configure Build Path
3) Libraries tab
4) Expand the "Plug-in dependencies", and select the "Access Rules: ..." item.
5) In the right menu, select "Edit"
6) "Add..." Button
7) Selecting resolution: "Accessible", and as rule pattern: "org/eclipse/xtext/builder/nature/**"

Rebuilding occurs. However, in my plugin.xml I *still* get that warning for discouraged access, even though I've added that rule. That is, the build path access rules are not checked by the plugin.xml builder :( And they should. Or not?

Comment 5 Eclipse Genie

2019-07-11 01:41:39 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.

--
The automated Eclipse Genie.