Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Platform-releng-faq-deprecated

Revision as of 05:16, 10 February 2022 by Akurtako.redhat.com (Talk | contribs) (Can I use update manager in my existing Eclipse 3.1 installation to upgrade to Eclipse 3.2?)

Deprecated content from the platform-releng-faq

Where can I learn how to use the packager?

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

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 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">

Back to the top