This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 155525 [details] Manifest just after Clean & Build Product Version: NetBeans IDE Dev (Build 201508200002) Java: 1.8.0_60-ea; Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Runtime: Java(TM) SE Runtime Environment 1.8.0_60-ea-b25 System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb) Test Case --> http://services.netbeans.org/synergy/client/app/#/case/2617/suite/1981/v/1 According to the expected result the manifest should contain extra jar files and this is not the case. Please see the attached picture.
Next test case (http://services.netbeans.org/synergy/client/app/#/case/2618/suite/1981/v/1) fails in the same way. There are no extra artifacts in the classpath.
Works for me, app manitest in jar file: Manifest-Version: 1.0 Ant-Version: Apache Ant 1.9.4 Created-By: 1.7.0_67-b01 (Oracle Corporation) Class-Path: lib/jfxrt.jar lib/javaws.jar lib/deploy.jar lib/plugin.jar X-COMMENT: Main-Class will be added automatically by build Main-Class: javaapplication18.JavaApplication18 There are 2 important points: 1st) The Project Properties/Build/Deployment "Keep JavaFX RT artifacts on Compile Classpath if not present by default" must be enabled. The option is added by JFX support and it presents only if the JFX is already enabled (at least one JFX project was created or opened). 2nd) The project platform needs to be JDK 7. In JDK 7 the jfxrt.jar is located in the jre/lib and is not on the boot class path. In JDK 8 the jfxrt.jar is located in the jre/lib/ext and is a part of the boot class path, so it's not added.