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

Bug 362298

Summary:

tycho-compiler-plugin complains about "Access restriction" on org.eclipse.emf.ecore.resource.Resource erroneously

Product:

z_Archived

Reporter:

Matheis D <ma>

Component:

Tycho

Assignee:

Project Inbox <tycho-inbox>

Status:

CLOSED INVALID

QA Contact:

Severity:

normal

Priority:

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
maven debug output with tycho-compiler-plugin complaining	none

Description Matheis D

2011-10-28 08:31:04 EDT

Build Identifier: 3.7.0 I20110613-1736 - tycho-compiler-plugin:0.13.0 - maven

tycho-compiler-plugin complains about "Access restriction" on org.eclipse.emf.ecore.resource.Resource erroneously:

the setup is as follows:
one plugin, one test-fragment.
Plugin depends on eclipse.emf.ecore:jar:2.7.0.v20110605-0747, the relevant "import org.eclipse.emf.ecore.resource.Resource;"
Access to this class is NOT restricted by the manifest of eclipse.emf.ecore:jar:2.7.0.v20110605-0747, but tycho-compiler-plugin complains about such a restriction.

Please see debug output in attachment.












Reproducible: Always

Comment 1 Matheis D

2011-10-28 08:32:18 EDT

Created attachment 206126 [details]
maven debug output with tycho-compiler-plugin complaining

Comment 2 Matheis D

2011-10-28 08:43:26 EDT

It seems that adding an explicit dependency to the plugin's manifest to org.eclipse.emf.ecore;bundle-version="2.7.0" removed the problem!

However, Eclipse IDE itself never complained about the restriction, even though the explicit dependency was NOT set before.

Strange!

Comment 3 Matheis D

2011-10-28 08:50:14 EDT

the debug output shows, that now the access restrictions are "more verbose" for org.eclipse.emf.ecore:

 D:\ide\maven_repo\p2\osgi\bundle\org.eclipse.emf.ecore\2.7.0.v20110605-0747\org.eclipse.emf.ecore-2.7.0.v20110605-0747.jar[+org/eclipse/emf/ecore/*;+org/eclipse/emf/ecore/impl/*;+org/eclipse/emf/ecore/plugin/*;+org/eclipse/emf/ecore/resource/*;+org/eclipse/emf/ecore/resource/impl/*;+org/eclipse/emf/ecore/util/*;+org/eclipse/emf/ecore/xml/namespace/*;+org/eclipse/emf/ecore/xml/namespace/impl/*;+org/eclipse/emf/ecore/xml/namespace/util/*;+org/eclipse/emf/ecore/xml/type/*;+org/eclipse/emf/ecore/xml/type/impl/*;+org/eclipse/emf/ecore/xml/type/internal/*;+org/eclipse/emf/ecore/xml/type/util/*;?**/*]


Well, could this behaviour still be called a bug?