Jump to: navigation, search

Difference between revisions of "Platform-releng-faq-deprecated"

m
(added a few pages to "deprecated" FAQ)
 
Line 94: Line 94:
 
         mirrorsURL="http://www.eclipse.org/downloads/download.php?file=/eclipse/testUpdates&format=xml">
 
         mirrorsURL="http://www.eclipse.org/downloads/download.php?file=/eclipse/testUpdates&format=xml">
 
</source>
 
</source>
 +
 +
==How does the platform team create the source build?==
 +
See [[Platform-releng-sourcebuild]] (no longer valid)
 +
 +
==How do you run the source build for 3.5 builds?==
 +
See [[Platform-releng-sourcebuild35]] (no longer valid)

Latest revision as of 11:29, 28 March 2013

Deprecated content from the platform-releng-faq

What do I need to do to use org.eclipse.releng.basebuilder from HEAD now that the Xerces plugin has been removed?

If you use the org.eclipse.releng.basebuilder in your builds and you use TestVersionTracker to create a test.properties file (search for "TestVersionTracker" in your customTargets.xml build scripts), please read on.

Some older versions of the TestVersionTracker class required Xerces on the classpath. We have removed the Xerces jars from the HEAD stream only of org.eclipse.releng.basebuilder.

For any team broken by this, a <generateTestProperties> custom Ant task has been created which does the same. It is available in the org.eclipse.releng.basebuilder/plugins/org.eclipse.build.tools plug-in from HEAD. To use all you will need to do is the following replacement:

Replace text such as this (taken from GEF):

<property name="build.compiler" value="org.eclipse.jdt.core.JDTCompilerAdapter"/>
<javac
        verbose="true"
        failonerror="true"
        srcdir="${builderDirectory}/tools"
        destdir="${builderDirectory}/tools" 
        classpath="${eclipse.home}/plugins/org.apache.xerces_4.0.13/xercesImpl.jar:${eclipse.home}/plugins/org.apache.xerces_4.0.13/xmlParserAPIs.jar"/>
<java classname="TestVersionTracker">
    <arg line="${workingDirectory}/eclipse/features/org.eclipse.gef.test_3.1.0/feature.xml ${buildDirectory} ${workingDirectory}/gef-testing/test.properties" />
    <classpath>
        <pathelement path="${eclipse.home}/plugins/org.apache.xerces_4.0.13/xercesImpl.jar:${eclipse.home}/plugins/org.apache.xerces_4.0.13/xmlParserAPIs.jar:${builderDirectory}/tools" />
    </classpath>
</java>

with this:

<generateTestProperties
        buildDirectory="${buildDirectory}"
        featureId="org.eclipse.sdk.tests"
        outputFile="${workingDirectory}/eclipse-testing/test.properties"/>


Where can I learn how to use the packager?

http://wiki.eclipse.org/index.php/Platform-releng-packager

Platform Releng Galileo Plan

Galileo plan


Eclipse 3.5 releng retrospective

[3.5 retrospective]

Process to add a new platform to the build

Adding a new platform to the build


How is a new platform added to the build?

Adding another platform to the build, because we just need more


How do I update from 3.1 to 3.1.1 or 3.1.2 using update manager?

Refer to this document http://www.eclipse.org/eclipse/platform-releng/updatesfor3.1.1.html

Can I use update manager in my existing Eclipse 3.1 installation to upgrade to Eclipse 3.2?

No.

Why not? The existing update manager can only update plug-ins and features, not files such as the Eclipse executable. See bug 123162 for additional details.

The good news is that if you download the platform runtime or Eclipse SDK for 3.2, you can install the Callisto components you are interested in using update manager. See the Callisto page for more details.

How can I run the update manager from a command line to mirror a remote site?

Refer to running update manager from command line in Eclipse Help for the latest information. It copies the appropriate versions of features and associated plugins you specify and generates the site.xml. For instance, if you wanted to create an update site for the platform feature.

/home/kmoir/IBMJava2-142/jre/bin/java -cp plugins/org.eclipse.equinox.launcher_currentqualifier.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command mirror -from http://eclipsebuildserv.ottawa.ibm.com/testupdates -to /home/kmoir/update -featureId org.eclipse.platform -version 3.2.0.v20060525a-_OZ2g6CPhlzUdGe -ignoreMissingPlugins true

I specify ignoreMissingPlugins as true because we have several plugins in our platform feature which are not contributed as part of the build. For instance, the org.eclipse.swt.solaris.gtk.x86 fragment is built by the a team that has access to the hardware and contribute the drops post-build.

You can also mirror an entire site, for instance Callisto with the following command.

/home/kmoir/jdk1.4.2_03/jre/bin/java plugins/org.eclipse.equinox.launcher_currentqualifier.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command mirror -from http://download.eclipse.org/callisto/releases  -to /home/kmoir/site -ignoreMissingPlugins true

However, if you are interested in having a local replica of Callisto at your site, the better approach would be to mirror the Callisto update site via rsync. This will ensure that all updates are replicated automatically and you'll avoid running update manager scripts from the command line. Refer to the becoming an eclipse mirror page to pursue this option.

Running update manager from the command line will not copy packed jars if they exist. To generate the packed jars in the newly mirrored update site from the conditioned jars, run the following command with a Java 1.5 vm.

/home/kmoir/jdk1.5.0_06/jre/bin/java -jar plugins/org.eclipse.equinox.launcher_currentqualifier.jar -application org.eclipse.update.core.siteOptimizer -jarProcessor -outputDir /home/kmoir/update -processAll -pack /home/kmoir/update

Then generate the digest

/home/kmoir/IBMJava2-142/jre/bin/java -jar /home/kmoir/eclipse3.2rc6/eclipse/plugins/org.eclipse.equinox.launcher_currentqualifier.jar  -application org.eclipse.update.core.siteOptimizer -digestBuilder -digestOutputDir=/home/kmoir/update -siteXML=/home/kmoir/update/site.xml

Ensure that your site.xml specifies that it uses pack200 and the specifies the location of the digest...for instance

<site
        pack200="true"
        digestURL="http://download.eclipse.org/testUpdates/"
        mirrorsURL="http://www.eclipse.org/downloads/download.php?file=/eclipse/testUpdates&amp;format=xml">

How does the platform team create the source build?

See Platform-releng-sourcebuild (no longer valid)

How do you run the source build for 3.5 builds?

See Platform-releng-sourcebuild35 (no longer valid)