Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "CBI"

(Initiative Goals)
(Notable Implementations)
Line 16: Line 16:
 
==Notable Implementations==
 
==Notable Implementations==
 
* [[CBI/Eclipse Platform Build]]
 
* [[CBI/Eclipse Platform Build]]
 +
* [http://www.fosslc.org/drupal/content/tycho-good-bad-and-ugly Video discussing JBoss tools use of Tycho]
  
 
==Preferred Build Technologies==
 
==Preferred Build Technologies==

Revision as of 16:52, 7 January 2012

The Eclipse Common Build Infrastructure (CBI) is an initiative combining technologies and practices for building Eclipse Software.

Initiative Goals

  1. Get all Eclipse projects building their software on Eclipse Foundation hardware.
  2. Use and provide reference examples of best of breed build technologies and processes.
  3. 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.

It is our hope that this project develops an offering that is compelling so that many projects will move to use it.

Resources

Notable Implementations

Preferred Build Technologies

Hudson

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.

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:

Related Topics and Links

Back to the top