Thomas, > * Is it still possible to run pure
java when running headless? We
> really want to avoid using shared libraries. Yes it is, though it does now have the
version number, I guess the discussion will be in the bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=173742.
> * 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?
Yes it is, It should be propagating
everything forward into java. If something is being swallowed by
the launcher, then that is a bug.
> * Is the exit-code propagated to
the invoker as it was in startup.jar? It should be, though looking at the
code I notice some cases where it is not, I have raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=173900.
> * What impact will the new launcher
have on performance? Will we see
> improvements compared to startup.jar or will
it be about the same? Performance should be about the same.
However, there is opportunity now for the splash screen to come up
sooner than it used to, so there could be a perceived improvement. This
bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=173103 is about making
this easier to do.
on 02/09/2007 06:12:43 PM:
> Hi Andrew,
> I want to verify a few things with the new launcher that I didn't
> any info on on the wiki. This is probably because my primary interest
> headless launching. So here's a few questions for you.
> 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
> > (*http://wiki.eclipse.org/index.php/Equinox_Launcher*) 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".
> > 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
> > startup.jar.
> > 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
> > See also the related wiki pages:
> > http://wiki.eclipse.org/index.php/Equinox_Launcher_Plan and
> > http://wiki.eclipse.org/index.php/Splash_Screen_Improvements.
> > -Andrew
> > ------------------------------------------------------------------------
> > _______________________________________________
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> cross-project-issues-dev mailing list