Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Equinox Launchers in 3.3 M5.

Hi Andrew,
I want to verify a few things with the new launcher that I didn't find any info on on the wiki. This is probably because my primary interest is headless launching. So here's a few questions for you.

   * Is it still possible to run pure java when running headless? We
     really want to avoid using shared libraries.
   * Is the new java launcher transparent to options? I.e. does it
     forward everything that it doesn't recognize? Does it propagate
     options that it does recognize and act on or are they swallowed?
   * Is the exit-code propagated to the invoker as it was in startup.jar?
   * What impact will the new launcher have on performance? Will we see
     improvements compared to startup.jar or will it be about the same?

Kind Regards,
Thomas Hallgren

Andrew Niefer wrote:

Hello All,

With the Eclipse 3.3M5 build coming very soon, I wanted to let everyone know about the changes that have been made to the eclipse launcher and startup. Please see the wiki page (**) for details.

For those who don't want to go that far, here are the major points:

   1. *There is no more startup.jar*.  Startup.jar is now a bundle
      org.eclipse.equinox.launcher.  The most immediate advantage to
      this is that startup.jar can now be updated from an update site.
       Eclipse can still be started from java, only now the command is
      something like "java -jar
      plugins/org.eclipse.equinox.launcher_1.0.0.v20070207.jar".  For
      those of you who have scripts that refer to startup.jar, it is
      possible to copy the launcher bundle into the root and name it
   2. *We are now using the JNI Invocation API*.  As much as possible,
      we will now attempt to dynamically load the jvm shared library
      and start the vm in the eclipse process using the JNI Invocation
      API.  The launcher will still fork java in a new process if the
      -vm argument points to a java.exe, or if we are unable to locate
      the jvm shared library.
   3. *SWT in the splash Screen.* We can now use SWT widgets in the
      splash screen.  The progress bar, build-id and the "Loading ..."
      text in the M5 splash screen are all done using SWT.

See also the related wiki pages: and


cross-project-issues-dev mailing list

Back to the top