IDE is the best example of a huge desktop application written in Java.
Most Java I usually launch applications with a batch or shell script to create a string with the class path of the application, and launch the GVM as a env variable with a class path.
Eclipse, hands on the other, depends on a basic launcher, why is it so? What does the launcher do that script do?
I remember reading an article about a year and a half ago I understood that "we are better than a native launcher", but the id did not say the internal work of the launcher.
Launcher uses JN to start Java VM in the same process. Using JNI also allows us to use SWT widget in the slash screen.
Actually, you can still have a script, because the launcher executable, eclipse.exe, has broken into 2 to 3.3 pieces. M5:
- Executable, and
- A Shared Library (Example: eclipse_1006.dll).
Executable Eclipse remains in the root of install.
The Shared Library is a platform specific piece, in org.eclise.equinox.launcher. [Config] , in the Plugins directory.
To move most launcher codes to a shared library that remains in one piece, this means that the part of the launch code can be updated from the update site. Also, while starting with Java, the shared library can be loaded via JNI to display a splash screen.
As explained here, you can,
java -jar plugins / org.eclipse.equinox.launcher_1.0.0.v20070319.jar Note that the name of the jar-file is now dependent on the version which is due to non-genuine scripts, which is used to break the jar-file after updating, using the correct filename Invites
instead you org.eclipse.equinox _ *. You can find the file matching Jar . Thankfully, Eclipse-Wiki is useful in this case.
If you want to avoid modifying existing scripts, you can also search the Equinox Launcher plug-in, copy it to the Eclipse main directory and change the copy to startup .jar.
Comments
Post a Comment