Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CBI"
(→Meeting Minutes) |
(→Initiative Goals) |
||
| Line 1: | Line 1: | ||
The Eclipse Common Build Infrastructure (CBI) is an initiative combining technologies and practices for building Eclipse Software. | The Eclipse Common Build Infrastructure (CBI) is an initiative combining technologies and practices for building Eclipse Software. | ||
| + | |||
| + | ==What is CBI== | ||
| + | |||
| + | The Common Build Infrastructure provides a Maven configuration file (pom.xml) to build Eclipse based projects and product. By using this file for your Tycho build you use the same setup as the Eclipse projects and benefit from their learning experience. CBI also make local builds very easy, which allow contributor and committers to build their own flavor of the Eclipse IDE. | ||
| + | |||
==Initiative Goals== | ==Initiative Goals== | ||
Revision as of 19:20, 27 November 2012
The Eclipse Common Build Infrastructure (CBI) is an initiative combining technologies and practices for building Eclipse Software.
Contents
What is CBI
The Common Build Infrastructure provides a Maven configuration file (pom.xml) to build Eclipse based projects and product. By using this file for your Tycho build you use the same setup as the Eclipse projects and benefit from their learning experience. CBI also make local builds very easy, which allow contributor and committers to build their own flavor of the Eclipse IDE.
Initiative Goals
Primary
- Make it really easy to contribute Eclipse projects
- Make it really easy to copy & modify source
- Make it really easy to build
- Make it really easy to test
- Make it really easy to post a change for review
- Make it really easy to sign software
Secondary
- Get all Eclipse projects building their software on Eclipse Foundation hardware.
- Enable the Long Term Support Program.
There is a strong link between CBI and the Long Term Support Program which enables a marketplace of companies providing maintenance and support for Eclipse technologies for durations far beyond typical community support. Please NOTE: CBI features will be available to community.
It is our hope that this project develops an offering that is compelling so that many projects will move to use it.
Next meeting
See the conference bridge details. Contact andrew dot ross at eclipse dot org if you would like to be added to the Calendar reminder. The dates the upcoming calls are as follows:
- November 15th, 9am EST
Resources
- mailing list cbi-dev
Bugs
- CBI 1.0
- CBI 2.0
- List of All Bugs (Product = CBI)
Tutorials, News, and other resources
- Tycho tutorial by Lars Vogel
- Video discussing JBoss tools use of Tycho
- Workshops being developed
- Building Eclipse SDK locally with Maven
- Sonar at Eclipse.org !
Eclipse platform CBI build
Preferred Build Technologies
Hudson
- The Eclipse Hudson instance; and
- Hudson projects using Maven and Tycho.
Maven
Maven 3.0 drives the builds. Projects are expected to provide standard Maven 3.0 POM files for their builds. The builds should be built in such a way that they can be run on the local workstation, or on the Eclipse build server. Note that builds can only be signed on the Eclipse build server.
- Parent Maven POM for Eclipse projects;
- Signing Builds using Maven; and
- Maven repository support at Eclipse.
Tycho
Tycho is focused on a Maven-centric, manifest-first approach to building Eclipse plug-ins, features, update sites, RCP applications and OSGi bundles.
Helpful links:
- Tycho project information, including demo projects; and
- Building Woolsey with Maven and Tycho
- Reference Card
- Packaging Types
Signing tool
Related Topics and Links
FAQ
- See your Frequently Asked Question list