Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357060 - Generated conflicting source dependencies are sometimes left out
Summary: Generated conflicting source dependencies are sometimes left out
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-08 07:14 EDT by Thomas Hallgren CLA
Modified: 2019-02-25 14:39 EST (History)
0 users

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 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.