As of http://download.eclipse.org/eclipse/downloads/drops4/I20150511-2130/
Eclipse starts again using the latest JRE 9.
Dani
From: Tom Schindl tom.schi...@bestsolution.at
To: equinox-dev@eclipse.org
Date: 07.05.2015 22:23
Subject:Re: [equinox-dev] Eclipse won't work on
No sorry this is not right. Alex and Tom’s answer was correct. Please refer to
section 4.4.6.2 of the OSGi Core R6 specification for details of the Lazy
Activation Policy and its impact on bundle lifecycle.
Unsatisfied imports such as in your example would cause a failure of
resolution,
Hmm, I would say they remain on such state due a missing class (or any
other problem while loading B in memory)
For instance, plugin A imports class B which imports class C. If C is not
available A will remain in the Starting state for ever.
El 12/5/2015 11:49, Lars Vogel lars.vo...@vogella.com
Surely the other answer was right and I confused both states. Thanks for
the clarification and sorry for my bad input :(.
2015-05-12 12:36 GMT+02:00 Neil Bartlett njbartl...@gmail.com:
No sorry this is not right. Alex and Tom’s answer was correct. Please
refer to section 4.4.6.2 of the OSGi
Thanks Alex and Tom for the clarification.
Best regards, Lars
On Fri, May 8, 2015 at 3:14 PM, Thomas Watson tjwat...@us.ibm.com wrote:
Alex is correct. Things in the STARTING state are waiting to be lazily
activated on first class define.
Tom
-equinox-dev-boun...@eclipse.org wrote:
