Skip to main content
Jump to: navigation, search

Difference between revisions of "Platform-releng-pack200"

m
m
 
Line 1: Line 1:
 
<h4>How did the platform releng team incorporated pack200 technology into our build process?</h4>
 
<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, with the exception of ones required by the test features. Here is an except from the script that runs the 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)
 
(Example is from org.eclipse.releng.eclipsebuilder/buildAll.xml v20060426a)
Line 13: Line 15:
 
<antcall target="signMasterFeature" />
 
<antcall target="signMasterFeature" />
 
<antcall target="unpackUpdateJarsForPackaging" />
 
<antcall target="unpackUpdateJarsForPackaging" />
<antcall target="buildUpdateSite" />
+
.....
</sequential>
+
<sequential>
+
<antcall target="buildMasterRootFeature" />
+
<antcall target="buildSdkTestFeature" />
+
<ant antfile="${eclipse.build.configs}/../helper.xml" target="verifyCompile" />
+
</sequential>
+
</parallel>
+
<parallel failonany="true">
+
<sequential>
+
<antcall target="packageEclipseDistributables" />
+
<antcall target="packageEquinoxDistributables" />
+
<antcall target="publishEclipse" />
+
<antcall target="publishEquinox" />
+
</sequential>
+
<antcall target="testEclipse" />
+
</parallel>
+
</target>
+
</pre>
+
  
  
The target signMasterFeature below currently just 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).
+
 
 +
 
 +
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>
 
<pre>
Line 58: Line 44:
 
</pre>
 
</pre>
  
 
The <i>unpackUpdateJarsForPackaging</i> task unpacks the jars with <i>unpack=false</i> in their features.
 
 
We then build an update site with the
 
  
 
<h4>Reference docs</h4>
 
<h4>Reference docs</h4>

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>


Reference docs

Pack200 Pack200

Update_Site_Optimization Update Site Optimization

Back to the top