Bug 264730 - [publisher] Ensure there is only 1 CU per host
Summary: [publisher] Ensure there is only 1 CU per host
Status: RESOLVED DUPLICATE of bug 252284
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 264746
  Show dependency tree
 
Reported: 2009-02-12 12:45 EST by Ian Bull CLA
Modified: 2009-04-27 11:33 EDT (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 Ian Bull CLA 2009-02-12 12:45:05 EST 
In ConfigCUsAction.perform we should ensure that we only publish one CU per host

 - In the case of conflicting advice, either merge or pick one.  Merging seems hard.  for now put in a method to do the merge flow but for now just return the first one.
 - consider merging createGeneratorBundleInfo into fillinBundles to simplify
 - remove the special case for Update configurator in publishBundleCUs.
Comment 1 Andrew Niefer CLA 2009-02-27 10:59:50 EST 
See bug 265864 comment #2:
"I also added a property "org.eclipse.pde.build.default=true" to every CU we generate.  I suggest using this to give priority to others when we find more than 1 CU, this is the easiest way I could think of to deal with some nested feature also providing CUs for these same bundles."

If we find more than one CU and one of them has this property, we can choose the other
Comment 2 Ian Bull CLA 2009-04-27 11:33:09 EDT 
Marking a duplicate of Bug 252284

*** This bug has been marked as a duplicate of bug 252284 ***