Jump to: navigation, search

Difference between revisions of "Modeling Project Releng/Building/All-In-Ones"

Line 3: Line 3:
 
If you prefer to create a more light-weight bundle, this is NOT the solution for you.
 
If you prefer to create a more light-weight bundle, this is NOT the solution for you.
  
::
+
:: -
 
::'''''PLEASE NOTE: If you plan to use this task, you MUST migrate your build to modeling.eclipse.org first, as there is insufficient space on emft.eclipse.org to accommodate this task. '''''
 
::'''''PLEASE NOTE: If you plan to use this task, you MUST migrate your build to modeling.eclipse.org first, as there is insufficient space on emft.eclipse.org to accommodate this task. '''''
::
+
:: -
  
 
To use this new Ant task, simply add this to your buildAll.xml:
 
To use this new Ant task, simply add this to your buildAll.xml:

Revision as of 17:07, 10 December 2008

As of December 2008, there's a new Ant task for packaging up All-In-One bundles. These archives consist of your SDK or ALL zip + Eclipse + all dependencies used to build.

If you prefer to create a more light-weight bundle, this is NOT the solution for you.

-
PLEASE NOTE: If you plan to use this task, you MUST migrate your build to modeling.eclipse.org first, as there is insufficient space on emft.eclipse.org to accommodate this task.
-

To use this new Ant task, simply add this to your buildAll.xml:

<ant target="packAllInOnes" antfile="${helper}" />

You can control the behaviour of the task with these options:

<property name="allInOnePrefix" value="${projectName}-all-in-one" />
<property name="allInOnePlatforms" value="win32,linux-gtk,macosx-carbon" />
<property name="allInOneInputs" value="${allZip}" />
<property name="allInOneBuildTypes" value="S,R" />

See also this script for more information -- search for "packAllInOnes".