Probably also issue on UI. User must be informed that in module list is selected
more clusters. The webstart work only on Platfrom. At least this failure should
be implemented in build script.
To show Error message box during "Run JNLP App" and "Debug JNLP App" will be nice.

I was talking about it with Yarda. For example the netbeans distribution
contains debugger. The debugger cannot be enabled on JNLP run. A exception was
thrown tha debuggerXXX module cannot be disabled and ide freezed. Another
problem I found with CLI. The IDE freezed when the CLI tried to connect localhost.

BTW nobody know that a netbeans module is webstartable. Why not to add the
information into module manifest?
webstartable: FALSE/TRUE
After that we can resolve what could be packed into jnlp distribution. Is only
idea. May be wrong.

I'm not sure what the resolution was on this issue when planning JWS support. It
may or may not be feasible to detect automatically that a given module cannot be
safely run under JNLP (using our current technology). Yarda?
Re. debugger - we ought to be able to detect that the module JAR requests some
JDK-only package, and refuse to package it.
Re. CLI - not sure what is going on here. Seems to me that it should be harmless
to package the module, but the CLI functionality will certainly not work. Not
sure why it would cause a freeze. Perhaps the jnlp launcher JAR needs to set
some flag in boot.jar requesting that the whole CLI infrastructure simply be
disabled? It is not appropriate for JNLP mode, I think. (There is a somewhat
analogous facility in JNLP itself, but it is probably not compatible with our
own system.) May be desirable to continue to use $userdir/lock to prevent
clobbering of settings from >1 simultaneous instance, but refuse to accept any
command-line options.

I fixed the build scripts. Now the JNLP build fails if ant or autoupdate are
used.
I do not want to make any changes to UI, as it has been agreed that the
ModuleList will not check any deps for 5.0 version.
In the original scope of 5.0, this issue is fixed, imho.

yes this issue is fixed. There should be more user friendly message than:
/usr/local/pzajac/newdev/dev/netbeans/harness/suite.xml:151: The following error
occurred while executing this line:
/usr/local/pzajac/newdev/dev/netbeans/harness/jnlp.xml:91: Cannot build JNLP for
module
/usr/local/pzajac/newdev/dev/netbeans/nb5.0/modules/org-netbeans-modules-ide-branding.jar
as these files are in module's NBM, but are not referenced from any path:
[shortcuts.pdf, core/locale/core_nb.jar, THIRD-PARTY.html, nbos2icons.zip,
netbeans.icns, netbeans.png, core/locale/updater_nb.jar, REDISTRIBUTION.html,
modules/locale/org-netbeans-core-windows_nb.jar, LICENSE.html]
BUILD FAILED (total time: 2 seconds)

The jnlp build fails on windows.
Ant's log:
Created dir: C:\Documents and
Settings\Administrator\feedreader-suite\build\jnlp\netbeans
E:\nb50\netbeans\harness\suite.xml:152: The following error occurred while
executing this line:
E:\nb50\netbeans\harness\jnlp.xml:91: Cannot build JNLP for module
E:\nb50\netbeans\platform6\core\core.jar as these files are in module's NBM, but
are not referenced from any path:
[core/core.jar]
BUILD FAILED (total time: 7 seconds)

Tried to build JNLP application for FeedReader application on Windows XP with
very latest continuous build (20050920-0117). Failed with this Ant log:
release:
netbeans:
Generating information for Auto Update...
jnlp-master:
jnlp:
E:\nb50\netbeans\harness\suite.xml:152: The following error occurred while
executing this line:
E:\nb50\netbeans\harness\jnlp.xml:175: The following error occurred while
executing this line:
E:\nb50\netbeans\harness\common.xml:230: Cannot build JNLP for module
C:\Documents and Settings\Administrator\a\build\cluster\modules\org-jdom.jar as
these files are in module's NBM, but are not referenced from any path:
[modules\org-jdom.jar, modules\ext\jdom.jar, config\Modules\org-jdom.xml]
BUILD FAILED (total time: 23 seconds)