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 "Platform-releng-pack200"
(start doc describing how platform incorporated pack200 into build process) |
m |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | How the platform releng team incorporated pack200 technology into our build process? | + | <h4>How did the platform releng team incorporated pack200 technology into our build process?</h4> |
| − | During our build process, we build a giant feature that includes all the jars that are required by the build | + | During our build process, we build a giant feature that includes all the jars that are required by the build (except those in test features). This jars within this feature are then signed (optional) and packed. |
| + | |||
| + | Here is an except from the script that runs the process... | ||
(Example is from org.eclipse.releng.eclipsebuilder/buildAll.xml v20060426a) | (Example is from org.eclipse.releng.eclipsebuilder/buildAll.xml v20060426a) | ||
| + | <pre> | ||
<target name="main" depends="init"> | <target name="main" depends="init"> | ||
<antcall target="buildEclipseSourceDrops" /> | <antcall target="buildEclipseSourceDrops" /> | ||
| Line 12: | Line 15: | ||
<antcall target="signMasterFeature" /> | <antcall target="signMasterFeature" /> | ||
<antcall target="unpackUpdateJarsForPackaging" /> | <antcall target="unpackUpdateJarsForPackaging" /> | ||
| − | + | ..... | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | |||
| + | The target <strong>signMasterFeature<strong> below currently just processes packs the master feature. (The signing portion will probably not be in place for 3.2 because there isn't enough time for other teams to adapt). | ||
| + | |||
| + | <pre> | ||
<target name="signMasterFeature" if="sign"> | <target name="signMasterFeature" if="sign"> | ||
<property name="archiveName" value="eclipse-master-${buildId}.zip" /> | <property name="archiveName" value="eclipse-master-${buildId}.zip" /> | ||
| Line 54: | Line 42: | ||
<delete dir="${packtmp}" /> | <delete dir="${packtmp}" /> | ||
</target> | </target> | ||
| + | </pre> | ||
| − | + | <h4>Reference docs</h4> | |
| − | + | <p> | |
| − | + | ||
| − | + | ||
| − | + | ||
[[Pack200 Pack200]] | [[Pack200 Pack200]] | ||
| + | </p> | ||
| + | <p> | ||
[[Update_Site_Optimization Update Site Optimization]] | [[Update_Site_Optimization Update Site Optimization]] | ||
| + | </p> | ||
Latest revision as of 14:04, 28 April 2006
How did the platform releng team incorporated pack200 technology into our build process?
During our build process, we build a giant feature that includes all the jars that are required by the build (except those in test features). This jars within this feature are then signed (optional) and packed.
Here is an except from the script that runs the process...
(Example is from org.eclipse.releng.eclipsebuilder/buildAll.xml v20060426a)
<target name="main" depends="init">
<antcall target="buildEclipseSourceDrops" />
<antcall target="buildMasterFeature" />
<parallel failonany="true">
<sequential>
<antcall target="signMasterFeature" />
<antcall target="unpackUpdateJarsForPackaging" />
.....
The target <strong>signMasterFeature<strong> below currently just processes packs the master feature. (The signing portion will probably not be in place for 3.2 because there isn't enough time for other teams to adapt).
<pre>
<target name="signMasterFeature" if="sign">
<property name="archiveName" value="eclipse-master-${buildId}.zip" />
<property name="packtmp" value="${buildDirectory}/packtmp" />
<mkdir dir="${packtmp}" />
<move file="${buildDirectory}/${buildLabel}/${archiveName}" tofile="${packtmp}/${archiveName}"/>
<!--pack200-->
<java jar="${eclipse.home}/startup.jar"
fork="true"
jvm="${java15-home}/bin/java"
failonerror="true"
maxmemory="128m"
dir="${buildDirectory}">
<arg line="-application org.eclipse.update.core.siteOptimizer"/>
<arg line="-jarProcessor -outputDir ${buildLabel} -repack ${packtmp}/${archiveName}"/>
</java>
<delete dir="${packtmp}" />
</target>