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

Bug 342586

Summary:	Tooling doesn't respect attributes on Im-/Export-Package headers in determining project dependencies
Product:	[RT] Virgo	Reporter:	Martin Lippert <mlippert>
Component:	tooling	Assignee:	Project Inbox <virgo-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	eclipse, mlippert
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:
Bug Depends on:
Bug Blocks:	368782

Description Martin Lippert

2011-04-12 10:50:06 EDT

While working on a scheme to use multiple bundle projects per lab in a workspace for an AP course, I tried to use attributes (OSGi spec section 3.6.5) to distinguish between multiple projects (start and solution, and also multiple start/solution projects for different labs) that im-/export the same packages.
Something like this:
[project a] Export-Package: hello.domain;lab=ap-bundle
[project b] Export-Package: hello.domain;lab=ap-web
[project c] Import-Package: hello.domain;lab=ap-bundle
[project d] Import-Package: hello.domain;lab=ap-web

Project c should depend only on a, d only on b. However, the tooling still gives me a classpath container for projects c and d that has both a and b listed as a dependent project. 
This is basically a show-stopper in developing the lab contents the way we envisioned, which is why I marked this as critical.

(moved over from: https://issuetracker.springsource.com/browse/STS-313)