Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355618 - Buckminster should not include update sites referenced from included features
Summary: Buckminster should not include update sites referenced from included features
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-24 04:35 EDT by Thomas Hallgren CLA
Modified: 2019-02-25 14:40 EST (History)
1 user (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 Thomas Hallgren CLA 2011-08-24 04:35:11 EDT 
The p2 publisher includes all update sites from all referenced features in the generated p2 repository. That introduces a lot of bloat. The eclipse.cvs feature for instance, references the updates/3.5. Many indigo features still reference helios etc.

The correct way to do this with Buckminster is to create a site feature and let that features 'sites to visit' determine what update sites that should be referenced in the generated repository. Buckminster should override the default p2 publisher behavior.
Comment 2 Henrik Lindberg CLA 2011-08-26 07:47:19 EDT 
I think this issue requires documentation.