JDK-8124647 : JRE 8 launcher doesn't load classes from the JavaFX-Class-Path attribute added to the manifest
  • Type: Bug
  • Component: javafx
  • Sub-Component: application-lifecycle
  • Affected Version: 8
  • Priority: P3
  • Status: Resolved
  • Resolution: Duplicate
  • Submitted: 2013-02-13
  • Updated: 2015-06-17
  • Resolved: 2013-11-14
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8Resolved
Related Reports
Duplicate :  
JDK-8102329 - Finish implementing changes to JavaFX launcher implementation
Duplicate :  
JDK-8117109 - FXMLLoader throws " java.lang.InternalError: CallerSensitive annotation expected at frame 1 "
Relates :  
JDK-8117109 - FXMLLoader throws " java.lang.InternalError: CallerSensitive annotation expected at frame 1 "
Description
JRE 8 launcher doesn't load classes from the JavaFX-Class-Path attribute added to the manifest.
Java throws NoClassDefFound exception.
It is impossible to run program that was built with javafxpackager.
ANT fx:jar task doesn't allow add Class-Path attribute to manifest (Java 7 version allows).

Forum discussion https://forums.oracle.com/forums/thread.jspa?threadID=2497521
Comments
We are resolving this issue in https://javafx-jira.kenai.com/browse/RT-34236, please verify fix works for this case as well once fix is pushed.
14-11-2013
https://javafx-jira.kenai.com/browse/RT-34236
14-11-2013
BTW, I'm not using the ant task, just using the javafxpackager command line tool.
23-08-2013
I don't know. There is no Class-Path attribute in the generated manifest, only JavaFX-Class-Path
23-08-2013
This sounds more like a bug in the ant task. The Class-Path attribute is preferred over JavaFX-Class-Path, the latter is only being supported for legacy purposes.
23-08-2013
I believe the problem is in the PackagerList.java file, line 269. It is replacing semi-colons and commas with spaces, but not colons.
23-08-2013
FYI, the problem is that the class path is separated by colons when they should be separated by spaces. If I patch my manifest file in this manner, it works.
23-08-2013
This is a real pain. Still planning a fix?
23-08-2013
This will be fixed by RT-27054
16-02-2013
Possibly related to: RT-27054 "Finish implementing changes to JavaFX launcher implementation"
13-02-2013
This is a regression.
13-02-2013