Whatever is currently in the rt.equinox.p2 repo stays with the p2 project IMO ;-)
Personally I don't see the advantage of making p2 a separate project under RT, but if the p2 leads want to do it it is fine by me. I don't think it will give you any more freedom than you have today. Tom From: Ian Bull <[email protected]> To: Equinox development mailing list <[email protected]>, Date: 12/07/2012 12:02 PM Subject: Re: [equinox-dev] Equinox Subprojects Sent by: [email protected] I certainly wouldn't be opposed to making p2 its own project, but how much extra overhead in involved (managerial -- release, docware, etc... and technical -- builds, platform contribution, etc..)? Also, there are a few components (simple configurator for example), which are kinda p2 and kinda platform and sorta equinox. I guess Pascal and Tom would have a good idea of where to place these things (they're in p2 right now). cheers, ian On Fri, Dec 7, 2012 at 12:07 AM, Gunnar Wagenknecht <[email protected] > wrote: Am 06.12.2012 23:46, schrieb Pascal Rapicault: Another solution is to make p2 a project in of itself. That's what I was thinking. -Gunnar -- Gunnar Wagenknecht [email protected] http://wagenknecht.org/ _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev -- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
