| Summary: | [Launcher] Publish the path to the native launcher | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Andrew Niefer <aniefer> |
| Component: | Framework | Assignee: | equinox.framework-inbox <equinox.framework-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | tjwatson |
| Version: | 3.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 205833 | ||
|
Description
Andrew Niefer
See bug 204341 attachment 79090 [details] This patch also uses the -launcher argument to set the osgi.install.area property. I think this is a better approach than the current assumption which is to set it to one directory up from the org.eclipse.equinox.launcher jar but only if the launcher is contained in the "plugins" directory. bug 204341 sets osgi.install.area, but this would not be sufficient for those that want the name of the launcher exe itself. We should define a second property, perhaps osgi.launcher? or org.eclipse.equinox.launcher.exe? I agree. I was pointing out another reason we would want to process the -launcher argument is to set the osgi.install.area but I agree we probably need another property set to indicate the launcher path. For better or worse we have not used fully qualified org.eclipse.* properties. Typically we use eclipse.* properties for eclipse specific properties. I suggest "eclipse.launcher". Done in head, property is eclipse.launcher |