Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Talk:Equinox Launcher Plan
Revision as of 10:54, 22 November 2006 by Aniefer.gmail.com (Talk | contribs)
What's the rationale for not parsing the Manifest.MF to obtain the Main-Class, and instead having it as a specific argument? Is it just for speed? If so, how much difference does it make? I'd have thought a RegExp would be fairly quick.
- We would like to avoid having to parse the manifest file mostly for simplicity's sake. To parse the manifest would would first need to extract it from the jar. Easy enough in Java, but a little more complicated in C. We don't really have time to write something like that ourselves. Admittedly I haven't looked, but I'm not sure that there's a library that we could use that covers all the platforms. Aniefer.ca.ibm.com 22:37, 21 November 2006 (EST)
- After thinking about this a little last night, I realized that we don't need to get the manifest using native C. The idea is that after creating the VM, but before looking for the Main class, we could use JNI reflection to get the manifest. Aniefer.ca.ibm.com 09:54, 22 November 2006 (EST)