Working around https://javafx-jira.kenai.com/browse/RT-29618 by generating a jar with Maven with the classpath in the manifest, and then letting fx:jar inject the necessary JavaFX classes and manifest entries, I succeeded in creating a native bundle with 2.2.6-ea. On Mac OS X I get a working .dmg but on Windows 7 (32&64bit) this results in an exe file that doesn't startup. There are no errors, the busy mouse pointer appears for a few seconds and then nothing. I did notice that the generated package.cfg contains an empty entry for app.classpath:
app.mainjar=myapp-0.9.9.jar
app.version=0.9.9
app.id=MyApp
app.mainclass=com/javafx/main/Main
app.classpath=
Don't know if this is normal or not.
As inRT-29618, just executing the same build targets with 7.0.17 results in a working exe file.
app.mainjar=myapp-0.9.9.jar
app.version=0.9.9
app.id=MyApp
app.mainclass=com/javafx/main/Main
app.classpath=
Don't know if this is normal or not.
As in
- duplicates
-
JDK-8125821 The Windows launcher generated by the packager fails when called with no parameter
-
- Closed
-