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.
As of now promotion of an application has to be done manually and it can not be done by simply copying html/jnlp files to other location. Currently these has to be manually edited before uploading to web site. Obviously One of the biggest JNLP issues is the fact that the absolute URL has to be part of the jnlp file. If this could be fixed, the overall usability would improved and Export app features won't be necessary or the UI could be really simple. However, if no improvements can be made in JNLP infrastructure itself the IDE could help by either packaging it as a WAR or providing some other post-processing that would make the application ready for deployment. Also could strip out classpath entries in manifest files. Again, Java WebStart shouldn't be looking at manifest files at all, but if we can't change that behavior the IDE should strip out offending entries from the manifest files during post-processing.
1. NetBeans are not responsible for Manifest, Jars or JNLP generation - that is job for JavaFX Packager. 2. JavaFX Packager provides all distribution Jars according to the "Application Model" team (an extra category in JavaFX Jira). 3. Any problems with the model should be reported to Jira on the Application Model category and any proposals must take in account all methods of JavaFX Execution/Debugging on all supported platforms and emulators.
I think, this mainly refers to java JNLP packaging, which is done by NetBeans
There are some differences between "active development" and "deployment" scenarios that has to be taken into consideration. Working on application developers wants: 1) Always be running latest version of its app (i.e. foreground update check, otherwise jars will be taken from the cache) 2) Do not want any remote access to runtime (i.e. local runtime and javascript) 3) Do not want to polute own desktop due to debug runs (desktop shorcuts must be off) 4) Prefer faster build time over result jar size (i.e. pack200 is not needed) For application deployment goals are different: 1) Minimize download size (i.e. use pack200, etc) 2) Use latest FX runtime (refer to javafx.com) 3) faster startup using cached copy (i.e. use background update check) NB should distinguish between these scenarios (not limited to items above). If any of these require changes in the underlying runtime and can not be workaround in the NB then please file issues on the runtime, etc. Do not depend on reporters to report this to all other places.
Changing the default component owner to tzezula.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss