Re: [cross-project-issues-dev] Juno 4.2 aggregation

[David M Williams <david_williams@xxxxxxxxxx>]

Same place, if I understand the question
... same b3aggrcon file. Things in Juno aggregation should be for only
4.2 (if, it does not work for both). If you have 3.8 users that need your
3.8 specific site, you will have to have some directions on your website
that explains what they should add to their software repository list. 

You _might_ have to do something special
to prevent your 4.2 version from automatically being offered as an upgrade
from your 3.8 version ... if in fact that's a bad thing. See Bug 371361
for how the eclipse SDK does that
... in short, adds following to p2.inf file of sdk features, so extra update
data (restrictions) published to Juno p2 repository  (Users can still
"manually" choose to install/upgrade to it, if they wish ...
just won't automatically be offered by "check for udpates". 

udpate.id = org.eclipse.platform.sdk
update.range = [4.0,4.3)
update.severity = 0
update.description = Restrict range so we are not an update for 3.x.

HTH




From:      
 Mark Russell <mrrussell@xxxxxxxxxx>
To:      
 Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>, 
Cc:      
 Eric Clayberg <clayberg@xxxxxxxxxx>
Date:      
 06/01/2012 02:45 PM
Subject:    
   [cross-project-issues-dev]
Juno 4.2 aggregation
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

I have added the WindowBuilder RC3 to the Juno Aggregation.
 I have a directory for WindowBuilder Eclipse 3.8 and one for WindowBuilder
Eclipse 4.2. In the aggregater I point to the 3.8 P2 repo where do I enter
the eclipse 4.2 repo to get it in to Juno Aggregation?

-- 
Mark R Russell
(724) 473-3140
Software Engineer in Test
Google Pittsburgh

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev