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.
I made a simple test module to call my website from the menu bar, as you can see from the code snippet below... ... public void performAction() { try { URL me = new URL("http://jcoolsoft.com"); HtmlBrowser.URLDisplayer.getDefault().showURL(me); } catch (MalformedURLException ex) { Exceptions.printStackTrace(ex); } } ... Then I tried to run-jnlp from my modules suite container. I get the following error. I remind you, this is only a small test module. I have in the wings a very large application that needs to be planted onto our company's server for WebStart deployment. This so far is a "major" show-stopper, so it seems. Can you help point me in the right direction? C:\Program Files\NetBeans 6.1\harness\suite.xml:347: The following error occurred while executing this line: C:\Program Files\NetBeans 6.1\harness\jnlp.xml:173: Cannot build JNLP for module C:\Program Files\NetBeans 6.1\ide9\modules\org-netbeans-modules-extbrowser.jar as these files are in module's NBM, but are not referenced from any path: [modules/lib/extbrowser.dll, modules/lib/extbrowser64.dll] BUILD FAILED (total time: 17 seconds)
Well, this is strange (I thought I already replied). Anyway, those dll's contain native code, which is used by NbDdeBrowserImpl. It seems that the jnlp build failure and complaint about that those dll are not in some paths, is not relevant. Passing to jnlp owner (I don't know where that belongs, please, reassign).
Building JNLP against a plain local copy of the platform currently works in case you are using only the platform cluster. It does not work in general if you use other clusters, depending on which modules you try to include, as specific modules like extbrowser need to be packaged in a special way for JNLP usage (in this case to bundle *.dll). Unless and until we distribute JNLP fragments as part of the regular IDE/Platform build, there is no way this can work except in limited cases. Instead you can specify jnlp.platform.codebase in your suite and point to a special build of the platform as JNLP fragments; currently platform and ide clusters are built in this way, and the extbrowser module should work in this mode (though this is rarely if ever tested - YMMV). For example, see the definition of <nativelib> in: http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastStableBuild/artifact/nbbuild/build/jnlp/org-netbeans-modules-extbrowser.jnlp/*view*/ which was created specially by extbrowser/build.xml. It appears there is no premade JNLP build for NB 6.1 on our download servers (i.e. http://www.netbeans.org/download/6_1/jnlp/ does not exist). You can make your own from 6.1 sources by running the 'build-jnlp' target, or use 6.0 or 6.5 dev JNLP builds.
Improving summary.