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

Bug 331013

Summary:	Aggregator should use private p2 profile when loading repositories
Product:	[Technology] CBI	Reporter:	Michal Ruzicka <michal.ruza>
Component:	CBI p2 Repository Aggregator	Assignee:	Project Inbox <b3.aggregator-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	miles.daffin, thomas
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Michal Ruzicka

2010-11-24 08:57:58 EST

Aggregator apparently (mis)uses the p2 profile of the Eclipse IDE (or the headless aggregator) installation to load the repositories referenced from an aggregation definition file.
As soon as I open an aggregation definition file, the "available software sites" list is polluted with all the repositories referenced from that file.
This makes it impossible to update/install new software into the IDE without careful deletion of the added software sites/p2 repositories because of conflicting components found in those repositories.
Agregator should not pollute the p2 profile used by the IDE to manage itself, instead it should create its own private p2 profile, maybe even multiple ones - a separate one for each aggregation definition file it processes.

Comment 1 Thomas Hallgren

2011-07-09 09:13:16 EDT

The aggregator now uses its own agent at location "${user.home}/.b3/p2agent" and will no longer interfere with the IDE installer. The location is currently hard-coded and should be settable using preferences. See bug 308872.

Fixed in revision 1514.

Comment 2 Miles Daffin

2011-07-14 17:19:56 EDT

I can confirm that the pollution of the p2 profile has now ceased! Excellent! This makes is much easier to maintain my Aggregation Eclipse install.

Comment 3 David Williams

2016-09-16 15:59:34 EDT

[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI.
No change to assignee for resolved and verified bugs.]