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.
The manifest in the main jar file in web start projects is not being generated correctly starting with version 6.9. The mainfest is referring to the INDEX.LIST file. The INDEX.LST file does not include the lib directory when referencing other jar files than the main jar. The JNLP jar references are generated correctly. This leads the initial installation to download all dependencies as specified in the JNLP file, but when starting the application, it is attempted to retrieve jar files from the web server with an incorrect path ("lib/" is missing). How to reproduce: -Prepare a local web server for hosting static files (the JWS deployment package) -Open the MarsRoverViewer project. -Enable web start and self signing. -Select a user defined codebase (eg, http://localhost/mars) -Build the project --You can then see that tha JNPL is correct, but the INDEX.LST in MarsRoverViewer.jat/META-INF/INDEX.LST does not contain the full path to the required jar files. -Make the files available through the web server. Make sure that the codebase and server config matches -Monitor the web server access log -Install/start the application -- You will now see a lot of attemtps to download jar files on invalid paths. This can lead to a lot of problems. Especially if the download area is protected with basic authentication and/or if the application actually should be started in offline mode.
Works fine for me. 1) I've created a new library project 2) I've created a new Java app project 3) Add the lib into the app project 4) Built the project 5) java -jar App works fine, loads classes from lib project and executes them.. You probably have the problems described in the issue #190461.
Sorry wrong issue. Reopening.
The problem is that the Ant jar task to do the index correctly requires (Class-Path attribute in the manifest.mf). This attribute was removed by JWS performance team due to some bug in the JWS causing eager loading of jars when they are on manifest's Class-Path. :-( I will return it back, hopefully the JWS is already fixed.
Thanks for the report, no one has tested the index after the performance fix. Fixed jet-main 6dd6eb5a77b9 You will need to regenerate the jnlp-impl.xml (disable JWS, delete it, enable JWS).
*** Bug 193715 has been marked as a duplicate of this bug. ***