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 Nick,
and thanks. To be honest, this looks horrible. Would it be possible for the equinox team to provide a unified way of launching using pure Java? I.e. reinstate the startup.jar as a very thin wrapper who's responsibility is to find the real launcher jar. Perhaps name it 'eclipse.jar'? In any case, put it in the root. Not everyone loves an executable and shared libraries.

Or perhaps I'm missing something. Is there some other unified way of booting the OSGi framework that doesn't involve finding a jar with some specific version and copy that to the root?

Kind Regards,
Thomas Hallgren

Nick Boldt wrote:

On behalf of the equinox guys, let me give you my "end-user" experience.

    * Is it still possible to run pure java when running headless? We
      really want to avoid using shared libraries.

See bugs and for some
progress made along these lines. The short answer for running headless
w/ <java jar="..." .../> instead of <exec
executable="${eclipse-home}/eclipse" .../> is that it's possible, as
discussed here:

    * 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?

I saw at least one example where an old commandline flag, "-noupdate",
is no longer supported and causes problems when running with the new
launcher jar. Links regarding what's supported and what's not are in
the wiki and bug 170831.

Hope that helps!

Nick Boldt :: Release Engineer, IBM Toronto Lab
Eclipse Modeling ::
cross-project-issues-dev mailing list

Back to the top