Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CBI"
(→Meeting Minutes) |
|||
Line 70: | Line 70: | ||
* [http://wiki.eclipse.org/EclipseLTS Long Term Support] | * [http://wiki.eclipse.org/EclipseLTS Long Term Support] | ||
* [http://wiki.eclipse.org/Build_Technologies List of Build Technologies] | * [http://wiki.eclipse.org/Build_Technologies List of Build Technologies] | ||
+ | |||
+ | ==FAQ== | ||
+ | |||
+ | * See your [http://wiki.eclipse.org/CBI/FAQ Frequently Asked Question list] | ||
==Meeting Minutes== | ==Meeting Minutes== |
Revision as of 14:10, 3 July 2012
The Eclipse Common Build Infrastructure (CBI) is an initiative combining technologies and practices for building Eclipse Software.
Contents
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
- Bi-weekly conference call, Tuesdays 10:00 to 11:00 Eastern timezone. Conference bridge details. Contact andrew dot ross at eclipse dot org if you would like to be added to the Calendar reminder.
- Code Sprint #2 - in July, 2012
GSoC
There are opportunities for students interested in participating in Google Summer of Code. Please see our list of project ideas and scan for CBI.
Resources
- mailing list cbi-dev
- List of Bugs (Product = CBI)
Notable Implementations
- CBI/Eclipse Platform Build see the CBI/Eclipse Platform Build Roadmap
- Video discussing JBoss tools use of Tycho
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