Community
Participate
Working Groups
This ticket will aggregate other tickets related to the Common Build Infrastructure build of the Eclipse platform.
Shouldn't this bug and the dependent bugs reside in the CBI bucket since the CBI team will be the ones actually doing the work?
That's a fair question Kim. My thinking was two fold: first, to help bring visibility of this work to people watching the platform but maybe not paying close attention on to the CBI product in bugzilla. Second, it made sense to have the ticket reflect the work being done & area affected more than the people doing the work. Please let me know if this is misguided thinking?
Well, the work to make the Platform build run under the CBI is actually being done by the people working on the CBI at the Eclipse foundation and Sonatype. I generally like to restrict the bugs in the platform releng bucket to ones that will be fixed within the Eclipse project itself. My understanding is that the CBI work will eventually be in closed forge that will be restricted to member companies that pay the appropriate fees for access.
(In reply to comment #3) > My understanding is that the > CBI work will eventually be in closed forge that will be restricted to member > companies that pay the appropriate fees for access. LTS (long term support) is the system that will be restricted. CBI (common build infrastructure) is the eclipse foundation infrastructure available to all eclipse projects. If this bug is tracking an eventual contribution to the Eclipse project of different build technology for *our* project build, then this seems like a reasonable place for the bug. I'll move it to Andrew for now to keep it out of your inbox.
Confirming the CBI work done on the Eclipse platform build will be contributed for consideration upstream. We'll need some assistance to ensure it can be accepted when ready. For those interested in the LTS IWG business model, I shared a presentation to the lts-iwg mailing list recently that outlines the model as it stands today. I'm doing a talk at the next members meeting about this. As well there's an informational session Wednesday afternoon in Reston Suites A at EclipseCon 2012.
(In reply to comment #3) > My understanding is that the > CBI work will eventually be in closed forge that will be restricted to member > companies that pay the appropriate fees for access. Kim, I just want to chime in to add to John and Andrew's replies. This is definitely _not_ the goal here. 100% of everything included in CBI will be made available to all Eclipse Foundation projects. Our goal is to offer this as a service to all Eclipse projects - including the Eclipse project. Our motivations are both altruistic and self-interested. Many projects over the years have expressed frustration with the difficulty of creating and maintaining builds. We hope to make that easier for the whole community. LTS is an important new program for Eclipse, and implementing it will be a lot easier if more projects share a common approach to builds. Hence, there is a relationship between LTS and CBI, but they are not the synonyms you think they are. My apologies for what is obviously an egregious miscommunication on our part.
Thanks for the clarification. It was a misunderstanding on my part :-)
*** Bug 374666 has been marked as a duplicate of this bug. ***
For reference, this item is on the Eclipse project Kepler plan. Here is the plan text: The Eclipse Foundation has established a common build infrastructure to be used by Eclipse projects. The aim is to simply the build process, and establish a common set of build technology and hardware across Eclipse projects. We will transition the Eclipse Platform build and automated tests to operate on this common infrastructure. This will make it easier for anyone to fetch and build the Eclipse Platform on any machine, and lower the long term maintenance cost of building older versions of Eclipse projects.
(In reply to comment #9) > For reference, this item is on the Eclipse project Kepler plan. Here is the > plan text: > > The Eclipse Foundation has established a common build infrastructure to be > used by Eclipse projects. The aim is to simply the build process, and s/simply/simplify/
Current CBI Platform build is heavily patched with maven-ant-runner and eclipse-runner invocations. I don't need to convince anyone that this approach is evil and will jeopardize the build in the long run. However, to replace majority of those calls with a fully fledged maven plugin, it is necessary to either rewrite everything from scratch (documentation generation, indexing, .apitools and possibly others) or to have latest Eclipse published to maven.eclipse.org and make it consumable for real maven plugins. We should handle this sooner than later.
(In reply to comment #11) > Current CBI Platform build is heavily patched with maven-ant-runner and > eclipse-runner invocations. I don't need to convince anyone that this > approach is evil and will jeopardize the build in the long run. See also bug 399150 PW
Since we are now regularly running Eclipse project builds using CBI this can be marked fixed for 4.3. There are other bugs that remain open to track various bugs and enhancements to the build.
(In reply to comment #13) > Since we are now regularly running Eclipse project builds using CBI this can > be marked fixed for 4.3. There are other bugs that remain open to track > various bugs and enhancements to the build. I won't "override" your setting, but IMHO, would be best to leave open and just untarget. Given all the open "depends on" bugs, still a good umbrella bug for "CBI work"? But, either way.
(In reply to comment #14) > I won't "override" your setting, but IMHO, would be best to leave open and > just untarget. Given all the open "depends on" bugs, still a good umbrella > bug for "CBI work"? But, either way. That's fine with me too. I just wanted to get it off the list of open 4.3 bugs!
*** Bug 393922 has been marked as a duplicate of this bug. ***
Marking as "fixed" as I think this bug has served its purpose. But, we won't sweep "work yet to do" under the rug, so will explicitly document that some of the bugs that were here, were simply moved to "the next" umbrella bug: Bug 434596 - Continuous improvement of build, and build process In other words, I'd say the major transition is done, but still lots to do to have a "state of the art", "good, complex example of", a Maven/Tycho build.
