|
|
(4 intermediate revisions by the same user not shown) |
Line 1: |
Line 1: |
− | The Eclipse Common Build Infrastructure (CBI) is a combination of technologies and practices for implementing builds of Eclipse projects.
| + | #REDIRECT [[CBI]] |
− | | + | |
− | Naturally, the CBI evolves over time. This page captures the current state-of-the-art CBI.
| + | |
− | | + | |
− | ==Build Technologies==
| + | |
− | | + | |
− | ===Hudson===
| + | |
− | | + | |
− | * The Eclipse [http://hudson.eclipse.org Hudson instance]; and
| + | |
− | * Hudson projects using [https://hudson.eclipse.org/hudson/view/Tycho%20+%20Maven/ 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.
| + | |
− | | + | |
− | * [[Maven/Parent POM|Parent Maven POM]] for Eclipse projects;
| + | |
− | * [[Minerva#Signing|Signing Builds]] using Maven; and
| + | |
− | * [[Maven|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|Tycho project]] information, including [[Tycho/Demo Projects|demo projects]]; and
| + | |
− | * [http://waynebeaton.wordpress.com/2010/09/23/building-woolsey-with-maven-and-tycho/ Building Woolsey with Maven and Tycho]
| + | |
− | | + | |
− | ==Build Practices==
| + | |
− | | + | |
− | TBD
| + | |
− | | + | |
− | ==Related Topics and Links==
| + | |
− | | + | |
− | * Long Term Support
| + | |