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.
Release32, build 7. 3 warnings show up on startup. The first one is a known bug (jaxp.jar is an empty file), the second one makes no sense since rt.jar is accessible; not locked and not empty. Regarding the last one, under OS/2 there is no %JAVA_PATH%\CLASSES so you should modify the installer to not use this path while running under OS/2. WARNING: lib\ext\jaxp.jar cannot be opened WARNING: d:\java13\JRE\LIB\RT.JAR cannot be opened WARNING: D:\java13\jre\classes cannot be opened
Warning of java module!?
A sort of. The warning is printed when JarFileSystem cannot be created from the classpath entry. Please try to open the rt.jar in some viewer - or even better list its contents using the standard jar utility.
I tried "unzip -t rt.jar" (infoZip) and it worked.. Furthermore, I ran "unlock" on it and it yielded no action which indicates that the file was not locked at the time of the problem. UNLOCK is a 3rd party util that's available for OS/2 and it forces the unlocking of a file; not safe but sometimes necessary. Perhaps there was some other sort of lock on the file I am not aware of but I know read-access was being allowed since UNZIP worked.
Anyway, if the warning is printed out, the parser is unable to open the JAR (whatever reason for). Could you, please verify that types are resolved correctly in source texts ? The most simple test would be make some class implement Comparable or something imported - code synchronization should pop up. Also (I think), Method Customizer displays fully qualified name in return type field (and in parameter types too, I think).
Two things to note: 1) This used to work with previous builds so it is probably a Netbeans bug 2) I created a class and made it implement Comparable.. Fine, that worked.. Then I pressed the DOWN arrow key and a dialog box poped up and asked me to add the function which Comparable defines. I selected OK. Name completion works through the problem. I hope that helps.. So it seems like RT.JAR is being accessed alright but we still get that Warning on startup so it might still break something down the line. This issue was introduced within the last 10-15 builds so whatever changes you've done recently probably lead to this..
I'll have the warning message printed with "informational" severity so it won't be shown unless NB is launched with some parameters.
The warning message is not shown under normal circumstances. However, it is worth investigating what has caused it.
Target milestone -> 3.2
Resolved for 3.4.x or earlier, no new info since then -> closing.