Summary: | Export to Mac .app bundle doesn't work with Mavericks (10.9) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> |
Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | daniel_megert, lshanmug, Michael_Rennie, rmraya, sarika.sinha |
Version: | 4.4 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Mac OS X | ||
Whiteboard: | stalebug | ||
Bug Depends on: | 441274 | ||
Bug Blocks: |
Description
Markus Keller
2014-04-03 13:55:57 EDT
Maybe the Mac app exporter could also use a shell script as launcher, see http://www.eclipse.org/swt/macosx/ . (In reply to Markus Keller from comment #1) > Maybe the Mac app exporter could also use a shell script as launcher, see > http://www.eclipse.org/swt/macosx/ . Or the other option is to get rid of the completely broken exporter altogether ;) See also bug 282050. Here is the commit for the exporter: http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=0bc6d15f67f4e9767873a2d0e312a90279c0f547 could not find any specific request for this support. The exporter relies on Java 6 from Apple, which uses JavaApplicationStub, but you are trying to run something coded with Java 7 from Oracle that does not use JavaApplicationStub to launch a Java-based application. You have to manually craft a launcher that embeds the JRE and uses a shelscript to launch the program. This has the advantage of being able to pass parameters to your program. Downside: if you have an SWT-based program it will not show the menu on start. Notice that Java 6 has already reached end of life. The current plan is to provide a wizard for the new Java Packager APIs from JDK 8u20, see bug 441274. Keeping this bug to get rid of the defunct export wizard. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. @Lakshmi, Do you still see this as a problem? |