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.
dev build 20010724 Tue Jul 24 21:39:50 EDT 2001: java.io.IOException: Referenced JAR file d:\netbeans\modules\icebrowser.jar could not be found java.io.IOException: Referenced JAR file d:\netbeans\modules\icebrowser.jar could not be found at org.netbeans.core.modules.ModuleList.readInitial(ModuleList.java:303) at org.netbeans.core.modules.ModuleSystem.readList(ModuleSystem.java:228) at org.netbeans.core.NonGui.run(NonGui.java:494) at org.netbeans.core.Main.run(Main.java:216) at org.openide.TopManager.initializeTopManager(TopManager.java:120) at org.openide.TopManager.getDefault(TopManager.java:81) at org.netbeans.core.Main.main(Main.java:322) at org.netbeans.core.TopThreadGroup.run(TopThreadGroup.java:90) [catch] at java.lang.Thread.run(Thread.java:498)
IceBrowser was removed from standard dev build of nb and is avaible only through autoupdate, so this is the reason why you see mentioned exception. Jesse, shouldn't be this better annotated to the user? Thanks.
Definitely it should and in fact I already have an uncommitted patch because I observed this from f4j IE 2 -> dev NB. With the patch it just prints one warning line and skips the module with no further ado. By the way Radim--are you sure you want to *remove* the module from builds completely? We have the opportunity to include it in builds but leave it disabled by default (though an existing user dir saying it was enabled would override this). IMHO at least little-used modules like RMI or similar should be handled this way, I don't know if the situation with icebrowser is comparable.
x
Should be fixed in the trunk.
Verified in dev #20010727, now in these cases will be following line printed on terminal: Warning: the module /export/home/LastNB/netbeans/modules/XXX.jar could not be found, ignoring...