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

Bug 353116

Summary: Fragment cannot compile against other fragment of same host
Product: z_Archived Reporter: Tobias Oberlies <t-oberlies>
Component: TychoAssignee: Project Inbox <tycho-inbox>
Status: NEW --- QA Contact:
Severity: minor    
Priority: P2    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
Project to demonstrate the issue none

Description Tobias Oberlies CLA 2011-07-26 10:19:02 EDT 
In the following situation, the compile class path is not set up correctly:
- Fragment B (with host H) imports package P
- Fragment A (with host H) exports the unique package P
-> A is missing on the compile class path of B.

The setup works if B is a fragment of a different bundle H2, or if B is a standalone-bundle.

Import-package on packages exported by fragments is a valid use case (this is the idea of import-package - you don't care where the package comes from), so this case should really work.
Comment 1 Tobias Oberlies CLA 2011-07-26 10:19:46 EDT 
Workaround: Manually add A to the compile class path of B through "jars.extra.classpath" in the build properties.
Comment 2 Tobias Oberlies CLA 2011-07-26 10:22:29 EDT 
Created attachment 200361 [details]
Project to demonstrate the issue
Comment 3 Tobias Oberlies CLA 2011-07-27 09:06:49 EDT 
Interestingly, PDE UI also doesn't cope with this situation - see bug 209140.
Comment 4 Mickael Istria CLA 2021-04-08 18:04:20 EDT 
Eclipse Tycho is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/tycho/issues/ instead. If this issue is relevant to you, your action is required.
0. Verify this issue is still happening with latest Tycho 2.4.0-SNAPSHOT
  if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done
  if issue is still present when latest release:
* Create a new issue at https://github.com/eclipse/tycho/issues/
  ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  ** In the GitHub description, start with a link to this bugzilla ticket
  ** Optionally add new content to the description if it can helps towards resolution
  ** Submit GitHub issue
* Update bugzilla ticket
  ** Add to "See also" property (up right column) the link to the newly created GitHub issue
  ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  ** Set status as CLOSED MOVED
  ** Submit

All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for Tycho will be archived and made read-only.