platform-update-home/doc/working/documentation/standalone_update.html
Parent Directory
| 
Revision Log
Revision 1.13 -
(download)
(as text)
(annotate)
Sat Sep 13 19:33:04 2003 UTC (6 years, 2 months ago) by dbirsan
Branch: MAIN
CVS Tags: v20040219
Changes since 1.12: +6 -3 lines
Sat Sep 13 19:33:04 2003 UTC (6 years, 2 months ago) by dbirsan
Branch: MAIN
CVS Tags: v20040219
Changes since 1.12: +6 -3 lines
*** empty log message ***
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Standalone update</title>
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
</head>
<body>
<h3>Standalone update</h3>
With the most recent code, you can install/update/enable/disable
a feature or list the features available on a remote site by running eclipse in a command line mode.<br>
You can also, mirror chosen features from an update site to a local update site mirror.<br>
<br>
Launch eclipse as follows, where [ ] means optional argument and arguments in italics must be provided by the user.<br>
<br>
<b>Installing a feature from a remote site</b>:<br>
java -cp startup.jar org.eclipse.core.launcher.Main <br>
-application org.eclipse.update.core.standaloneUpdate<br>
-command install <br>
-featureId <i>feature_id </i><br>
-version <i>version </i><br>
-from <i>remote_site_url</i> <br>
[-to <i>target_site_dir</i>] <br>
<p>
<b>Example:</b> <code>java -cp startup.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command install -from http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/optionalSite/ -featureId com.example.root -version 1.0.0</code>
</p>
<br>
<b>Updating an existing feature or all features</b>:<br>
java -cp startup.jar org.eclipse.core.launcher.Main <br>
-application org.eclipse.update.core.standaloneUpdate<br>
-command update<br>
[-featureId <i>feature_id </i>]<br>
<br>
<b>Enabling (configuring) a specified feature:</b><br>
java -cp startup.jar org.eclipse.core.launcher.Main <br>
-application org.eclipse.update.core.standaloneUpdate<br>
-command enable<br>
-featureId <i>feature_id </i><br>
-version <i>version </i><br>
[-to <i>target_site_dir</i>] <br>
<br>
<b>Disabling (unconfiguring) a specified feature:</b><br>
java -cp startup.jar org.eclipse.core.launcher.Main <br>
-application org.eclipse.update.core.standaloneUpdate<br>
-command disable<br>
-featureId <i>feature_id </i><br>
-version <i>version </i><br>
[-to <i>target_site_dir</i>] <br>
<br>
<b>Uninstalling a specified feature:</b><br>
java -cp startup.jar org.eclipse.core.launcher.Main <br>
-application org.eclipse.update.core.standaloneUpdate<br>
-command uninstall<br>
-featureId <i>feature_id </i><br>
-version <i>version </i><br>
[-to <i>target_site_dir</i>] <br>
<br>
In all the above commands where the -to target_site_dir is specified, corresponding
configured target site at given directory will be used. If it is not specified,
then the default local product site is used.<br>
<br>
If you only need to verify if the operation would succeed, in the above commands, (i.e. it satisfies the constraints), without actually performing it,
then add <b><em>-verifyOnly=true</em></b> to the list of arguments.<br>
<br><b>Searching a remote site, listing all available features for install:</b><br>
java -cp startup.jar org.eclipse.core.launcher.Main <br>
-application org.eclipse.update.core.standaloneUpdate<br>
-command search<br>
-from <i>remote_site_url</i> <br>
<br>
<b>Mirroring feature(s) from a remote site:</b><br>
java -cp startup.jar org.eclipse.core.launcher.Main <br>
-application org.eclipse.update.core.standaloneUpdate<br>
-command mirror<br>
-from <i>remote_site_url</i> <br>
-to <i>target_site_dir</i><br>
[-featureId <i>feature_id</i>]<br>
[-version <i>version</i>]<br>
[-mirrorURL <i>mirror_site_url</i>]<br>
<br>
If -mirrorURL is specified, an update policy will be generated in
<target_site_dir>/policy.xml file. The resulting policy.xml
maps all features from the mirror site to the specified URL.
The policy.xml can be used as is, or its fragments
can be included into custom designed policy file.
<br>
<br>
The return code for each command is either 0 (success) or 1 (failure).<br>
<br>
Additionally, most <A
href="http://dev.eclipse.org/help21/topic/org.eclipse.platform.doc.user/tasks/running_eclipse.htm">options
accepted by Eclipse executable</A> can be passed. They are especially
useful during debugging and for specifying target environment for installed features.
For example, passing option
<code>-ws gtk</code>
will set windowing system to GTK.<br>
</body>
</html>
| help@eclipse.org | ViewVC Help |
| Powered by ViewVC 1.0.3 |