Difference between revisions of "CBI/Projects"

From Eclipsepedia

< CBI
Jump to: navigation, search
(Tycho)
(Emphasise the Virgo is *not* moving to the CBI)
(15 intermediate revisions by 8 users not shown)
Line 19: Line 19:
 
* eclipse.platform.swt
 
* eclipse.platform.swt
 
* eclipse-parent
 
* eclipse-parent
* workspace
 
 
* eclipse.platform.releng
 
* eclipse.platform.releng
 
* eclipse.platform.swt.binaries
 
* eclipse.platform.swt.binaries
Line 39: Line 38:
 
===Mylyn===
 
===Mylyn===
 
===CDT===
 
===CDT===
===EGit===
+
===[[EGit]]===
===JGit===
+
 
 +
===[[JGit]]===
  
 
===Hudson===
 
===Hudson===
Line 52: Line 52:
 
===m2e===
 
===m2e===
 
repositories:
 
repositories:
<pre>
+
 
m2e-core             (confirmed)
+
* m2e-core
org.eclipse.m2e.wtp   (confirmed)
+
* org.eclipse.m2e.wtp
</pre>
+
 
 +
===e4 ===
 +
 
 +
org.eclipse.e4.tools
 +
 
 +
=== GMF Tooling ===
 +
 
 +
===Scout===
 +
repositories:
 +
* org.eclipse.scout-aggregator.git
 +
* org.eclipse.scout.rt.git
 +
* org.eclipse.scout.sdk.git
 +
 
 +
=== SWTBot ===
 +
 
 +
=== Nebula ===
 +
The Nebula build is using Tycho and Sonar. The build uses a continuous deployment strategy.
 +
 
 +
After source code is checked into the Nebula repository, the build is started automatically. The unit tests are executed and the resulting archives are automatically signed. After the signing process, the repository is pushed to the final location on download.eclipse.org where they can be consumed.
 +
 
 +
[[Nebula/Builds|Link to the Nebula build page.]]
 +
 
 +
=== [[Linux_Tools_Project|Linux Tools]] ===
  
 
==Projects that are moving to CBI==
 
==Projects that are moving to CBI==
  
===Stardust===
+
===[[Stardust]]===
===Virgo===
+
 
 
===WTP===
 
===WTP===
 +
 +
==Projects that are not moving to CBI==
 +
 +
===Virgo===

Revision as of 12:38, 22 February 2013

Contents

Projects that are using CBI today

Eclipse (platform)

These are the repositories included:

  • eclipse.platform.runtime
  • maven-cbi-plugin
  • eclipse.platform
  • eclipse.platform.team
  • eclipse.jdt.core
  • eclipse.platform.ui
  • eclipse.platform.ua
  • eclipse.platform.releng.tychoeclipsebuilder
  • eclipse.platform.common
  • rt.equinox.bundles
  • eclipse.pde
  • rt.equinox.binaries
  • eclipse.platform.text
  • eclipse.platform.swt
  • eclipse-parent
  • eclipse.platform.releng
  • eclipse.platform.swt.binaries
  • eclipse.platform.resources
  • scripts
  • eclipse.platform.releng.eclipsebuilder
  • eclipse.jdt
  • rt.equinox.p2
  • eclipse.platform.debug
  • rt.equinox.framework
  • eclipse.pde.build
  • eclipse.pde.ui
  • eclipse.jdt.debug
  • eclipse.jdt.ui
  • rt.equinox.incubator
  • eclipse.platform.repository
  • eclipse.jdt.core.binaries

Mylyn

CDT

EGit

JGit

Hudson

Tycho

repositories:

  • org.eclipse.tycho
  • org.eclipse.tycho-demo
  • org.eclipse.tycho.extras

m2e

repositories:

  • m2e-core
  • org.eclipse.m2e.wtp

e4

org.eclipse.e4.tools

GMF Tooling

Scout

repositories:

  • org.eclipse.scout-aggregator.git
  • org.eclipse.scout.rt.git
  • org.eclipse.scout.sdk.git

SWTBot

Nebula

The Nebula build is using Tycho and Sonar. The build uses a continuous deployment strategy.

After source code is checked into the Nebula repository, the build is started automatically. The unit tests are executed and the resulting archives are automatically signed. After the signing process, the repository is pushed to the final location on download.eclipse.org where they can be consumed.

Link to the Nebula build page.

Linux Tools

Projects that are moving to CBI

Stardust

WTP

Projects that are not moving to CBI

Virgo