| Summary: | [plan item] Provide update manager operations API | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jim des Rivieres <jeem> |
| Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Dorian Birsan <birsan> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | celek, danrubel, jasc, manahan, thatnitind, voutsin |
| Version: | 2.1 | Keywords: | plan |
| Target Milestone: | 3.0 M3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Jim des Rivieres
A requirement for the command line update from the mailing list:
* Impact Analysis (better integration with native installers basically)
- sometimes native installers may want to remove function from eclipse which
they
laid down. They need a way to ask eclipse if it is
a) ok to add or remove a feature
b) if it isn't ok some information that could be provided to the user to
assist
in making the decision regarding uninstall.
In the current command line support this would translate into an argument
(e.g. -simulate or -test) that would run validation step only and return 0 if
the validation is OK or some error code if issues are found.
In the former case, detailed report should be given (recursive dumping of
multi-status objects to stderr). This argument would be applicable to all the
operations that cause configuration changes (i.e. install, uninstall, enable,
disable).
The eclipse launcher allows running an IPlatformRunnable object, but there is no concept of return code, so theoretically, we the standalone update tool cannot return any kind of error codes. Perhaps we should either generate output to some predefined (or user supplied) file, or just output to stderr. It looks like if the return Object is of type Integer, that value would actually be returned. So, for the time being, the command line update application would return a status code of: 0 for a successful operation 1 for unsuccessul operation More error return codes can be added if needed. The current command line syntax is described at http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update- home/doc/working/documentation/standalone_update.html *** Bug 39347 has been marked as a duplicate of this bug. *** Just a note for those who picked up M2 and are experimenting with the command line update: Modify org.eclipse.update.core\plugin.xml (at the bottom of the file) so that org.eclipse.update.standalone.StandaloneUpdateApplication is replaced by org.eclipse.update.internal.standalone.StandaloneUpdateApplication The code has been available for quite a while and no feedback has been received, I will mark this as fixed. Please add your comments to this bug or open new bugs to address any issues. |