platform-update-home/doc/working/documentation/standalone_update.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.7 - (download) (as text) (annotate)
Wed Aug 13 17:31:05 2003 UTC (6 years, 3 months ago) by dbirsan
Branch: MAIN
Changes since 1.6: +2 -2 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>
 <br>
Launch eclipse as follows, where [ ] means optional argument and arguments in italics must be provided by the user.<br>
	<br>
<b>Note:</b> It is also recommended to invoke eclipse.exe with -nosplash and -vm path_to_java.exe
<br>
 <br>
<b>Installing a feature from a remote site</b>:<br>
 eclipse <br>
&nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate
<br>
&nbsp;&nbsp;&nbsp; -command install <br>
&nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
&nbsp;&nbsp;&nbsp; -version <i>version </i><br>
&nbsp;&nbsp;&nbsp; -from <i>remote_site_url</i> <br>
&nbsp;&nbsp;&nbsp; [-to <i>target_site_url</i>] <br>
	<p>
	<b>Example:</b> <code>eclipse.exe  -application org.eclipse.update.core.standaloneUpdate -nosplash -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>
  eclipse <br>
 &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate
<br>
 &nbsp;&nbsp;&nbsp; -command update<br>
 &nbsp;&nbsp;&nbsp; [-featureId <i>feature_id </i>]<br>
<br>
<b>Enabling (configuring) a specified feature:</b><br>
  eclipse <br>
 &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate
<br>
 &nbsp;&nbsp;&nbsp; -command enable<br>
 &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
 &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
 &nbsp;&nbsp;&nbsp; [-to <i>target_site_url</i>] <br>
<br>
<b>Disabling (unconfiguring) a specified feature:</b><br>
  eclipse <br>
 &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate
<br>
 &nbsp;&nbsp;&nbsp; -command disable<br>
 &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
 &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
 &nbsp;&nbsp;&nbsp; [-to <i>target_site_url</i>] <br>
<br>
<b>Searching a remote site, listing all available features for install:</b><br>
  eclipse <br>
 &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate
<br>
 &nbsp;&nbsp;&nbsp; -command search<br>
 &nbsp;&nbsp;&nbsp; -from <i>remote_site_url</i> <br>
<br>
In all the above commands where the -to target_site_url is specified, the
corresponding configured target site will be used. If it is not specified,
then the default local product site is used.<br>
<br>
The return code for each command is either 0 (success) or 1 (failure).
<br>
<br>
If you only need to verify if the operation would succeed (i.e. it satisfies the constraints), without actually performing it,
then add <em>-verifyOnly=true</em> to the list of arguments. 		
 
</body>
</html>