| Re: [cdt-dev] CDT Kepler on top of Eclipse Juno |
|
Hi Doug, Thanks for your update, your definition of 8.2 support for Juno as “second class but avoid breakage” sounds perfectly reasonable. In fact it is much in line with WTP’s definition in the WTP project plan. You are right that the Pin & Clone changes that Pawel is working on for Kepler Platform/Debug need to be in lockstep with Pin&Clone changes in CDT Kepler. Our idea to support this on top of Platform Juno would be that whoever deploys CDT 8.2 would also deploy the two Platform Debug plugins from Kepler. We’ve done initial validation that the Platform Debug plugins from Kepler run fine in a Juno Platform; And I’ve got confirmation from the Eclipse Platform PMC that such flexible mix and match of components should be possible. To quote John Arthorne, “Having
wider ranges of tolerance [in our bundle compatibility] is something we should be able to do (otherwise our plugin system is failing)” [1] Technically, it could be a “Patch Feature” delivered from the CDT Repo, which carries the Kepler debug plugins into the Juno Platform. Thanks for asking the question, I’ll be happy to talk about next steps; I suppose the next step would be setting up the Hudson Job to run CDT Kepler tests on Platform Juno. [1]
Jan 24 minutes,
http://wiki.eclipse.org/Eclipse/PMC Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River direct +43.662.457915.85 fax +43.662.457915.6 From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Doug Schaefer Hey Martin, We talked about this during the CDT call and decided that this was probably OK. I don't think we want to support it as a first class citizen, tough, since the vast majority
of user testing will be with the Kepler EPP package. But we will endeavour to fix anything that breaks compatibility with 3.8. The only area we were concerned about is if Pawel is working on anything new in the Platform Debug that we would need to adopt in Kepler. But given it's you who's asking
we're assuming that that is not the case? Doug. From:
<Oberhuber>, Martin <Martin.Oberhuber@xxxxxxxxxxxxx> Dear CDT Committers, We are interested in keeping the CDT 8.2 (Kepler) release compatible with last year’s
Eclipse Juno (4.2.2 and 3.8.2). The Eclipse Platform API has remained mostly unchanged since Juno, so the cost of this should be small – just one additional Hudson Verification Job to test CDT master against
Platform Juno every once in a while. On the other hand, we would become a lot more flexible, by being able to deploy new
CDT into older Eclipse (after all, Juno is the designated long-term support
stream, so some large companies are expected to stay on Eclipse Juno). A number of other Eclipse projects officially support the current Eclipse Platform as well as some older releases (N-1 or even N-2), most notably Mylyn and egit. WTP makes it very clear: http://www.eclipse.org/projects/project-plan.php?projectid=webtools#themes_and_priorities Would the CDT community support this approach, or are there any concerns ? Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect
– Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 |