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.
Difference between revisions of "Equinox Startup Issues"
(Initial Content from DJ) |
(→Background) |
||
| Line 5: | Line 5: | ||
One of the major downfalls of the Eclipse Update story is that it is not completely updateable; users are not able to use update manager to update between major releases. This was because the <code>startup.jar</code> was not a real bundle and not versioned. By moving the <code>startup.jar</code> code to the <code>plugins/</code> directory and making it a bundle, the update manager can now update this code in future releases of Eclipse. | One of the major downfalls of the Eclipse Update story is that it is not completely updateable; users are not able to use update manager to update between major releases. This was because the <code>startup.jar</code> was not a real bundle and not versioned. By moving the <code>startup.jar</code> code to the <code>plugins/</code> directory and making it a bundle, the update manager can now update this code in future releases of Eclipse. | ||
| − | + | The Equinox launchers were also designed to address the startup experience with respect to the splash screen. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154088 Bug 154088] was the plan item for this work. See also the wiki page on [[Splash Screen Improvements]]. | |
| − | + | ||
| − | + | ||
This work was previously outlined in [[Equinox Launcher]] and [[Equinox Launcher Plan]] as well as in messages sent to the mailing lists and outlined weekly in the Eclipse Architecture Meeting Minutes. It was first released to the Eclipse SDK builds in the first integration build after Eclipse 3.3 M4. (the integration build from December 19, 2006) | This work was previously outlined in [[Equinox Launcher]] and [[Equinox Launcher Plan]] as well as in messages sent to the mailing lists and outlined weekly in the Eclipse Architecture Meeting Minutes. It was first released to the Eclipse SDK builds in the first integration build after Eclipse 3.3 M4. (the integration build from December 19, 2006) | ||
Revision as of 12:33, 13 February 2007
Contents
Overview
As per bug 173742, some users are having issues when surrounding the move of the startup.jar from the root of the Eclipse install to the plugins/ directory. The purpose of this page is to outline the reasons for the move, the problems that people are having, and proposed solutions to these problems.
Background
One of the major downfalls of the Eclipse Update story is that it is not completely updateable; users are not able to use update manager to update between major releases. This was because the startup.jar was not a real bundle and not versioned. By moving the startup.jar code to the plugins/ directory and making it a bundle, the update manager can now update this code in future releases of Eclipse.
The Equinox launchers were also designed to address the startup experience with respect to the splash screen. Bug 154088 was the plan item for this work. See also the wiki page on Splash Screen Improvements.
This work was previously outlined in Equinox Launcher and Equinox Launcher Plan as well as in messages sent to the mailing lists and outlined weekly in the Eclipse Architecture Meeting Minutes. It was first released to the Eclipse SDK builds in the first integration build after Eclipse 3.3 M4. (the integration build from December 19, 2006)
Problems
Clients which scripts which started Eclipse directly from Java (java -jar startup.jar) must now be altered to point to the new JAR location.
Proposed Solutions
Bring back the old startup.jar
Revert from having a launcher bundle to having a startup.jar in the install root.
Create a new startup.jar
Write a new startup.jar which looks for the launcher bundle in the plugins/ directory and then calls it.
Do nothing
The story going forward would be that people who have products based on Eclipse and are starting Eclipse via Java directly would have to either modify their scripts to point to the correct launcher JAR or copy the launcher JAR to the Eclipse install root and rename it to be startup.jar.