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

Revision as of 11:42, 3 May 2010

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.