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

Bug 357060

Summary: Generated conflicting source dependencies are sometimes left out
Product: z_Archived Reporter: Thomas Hallgren <thomas>
Component: BuckminsterAssignee: buckminster.core-inbox <buckminster.core-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Thomas Hallgren CLA 2011-09-08 07:14:52 EDT 
Buckminster will include several versions of the same component unless some of them are optional. When that happens the optional component is excluded. This is per design and it supports several important use-cases. For source bundles however, this creates a problem.

Example:
1. Some SDK feature includes a source bundle. This inclusion is considered a
   required dependency.
2. The resolution finds two conflicting versions of some (non-source) bundle.
3. Since 'buckminster.download.source' is set to true, an optional dependency
   is generated for both bundles found in #2.
4. A conflict between the required source bundle from #1 and one of the
   optional source bundles generated in #3 occurs. The latter is now excluded.