Bug 342586 - Tooling doesn't respect attributes on Im-/Export-Package headers in determining project dependencies
Summary: Tooling doesn't respect attributes on Im-/Export-Package headers in determini...
Status: NEW
Alias: None
Product: Virgo
Classification: RT
Component: tooling (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 368782
  Show dependency tree
 
Reported: 2011-04-12 10:50 EDT by Martin Lippert CLA
Modified: 2012-01-16 18:38 EST (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 Martin Lippert CLA 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)