Pascal Rapicault wrote:
Which aspect are you interested in?
When you double click on the eclipse.exe, a
org.eclipse.equinox.launcher jar is being discovered from the
plugsins folder and is being executed (aka
org.eclipse.equinox.launcher.Main). This Main discover
org.eclipse.equinox loads it and starts it. After that osgi is given
control. When osgi starts it first restores the content from the
previous run from caches, reconciliates the lists of bundles
contained on the osgi.bundles property, and then raise the start
level. This causes the bundles to be started again.
HTH
PaScaL
Hi Pascal, really interesting stuff. I was not able to find such
startup process in Eclipse docs.
I was looking for such info because I was observing an interesting
behavior when Eclipse is starting up (to be more precise I am playing
with 3.4.2). It seems the time it consumes since I double click
eclipse.exe and the dialog asking for a workspace appears is really
bigger the first time I execute it. Since that first execution, the
next ones are really faster. But then, if I restart the machine, again
the first time will consume a lot.
Do you know which step is longer when it is executed the first time?
What is touched after a machine reboot that will affect the startup
process of Eclipse?
Is it possible to avoid that "time consuming" process and reuse
whatever info and/or cache from the previous machine session?
Thanks a lot,
Chemi.