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.
A jar's contents are removed when following these steps: 1 Mount a new filesystem Afs 2 Create a package, a 3 Add java class, A.java 4 Compile package 5 Create new jar content, ajar, containing package a 6 Compile jar content Afs a A.java ajar 7 Mount new filesystem Bfs 8 Create a new package, b 9 Add main java program, B.java 10 Edit B.java and add statement, import a.*; 11 Select ajar and copy paste it to base of filesystem Bfs Bfs b B.java ajar 12 Dismount filesystem Afs 13 Select filesystem Bfs and do Build Result Output window says "finished" nothing seemed to be compiled no B.class file ajar.jar now only contains Manifest. In step 13, if "Build-all" is done then the java file is compiled, but the jar is emptied.
Creating the second program is unnecessary. Simply mount filesystem Bfs and copy the jar from Afs to Bfs. Next unmount Afs, select ajar.jar and compile it ajar.jar is now empty.
A warning message is printed. Unfortuantely, it's printed to the output tab of the output window. Since the compiler window is selected during jar compilation it's effectively invisible.
The warning is now printed to both output and compiler tabs.
The jar file retains its contents. Jar recipe is marked with a red badge. This bug had been fixed. Note that ajar.jar file is also copied to bfs, can be mounted and B.java will compile. If the filesystem is selected and a build is done the jar recipe will also be compiled and this will fail. If the jar recipe is deleted then the jar is also deleted, despite ajar.jar still appearing as a mounted jar archive when in reality it no longer exists. Consequently, B.java won't compile.
verified as fixed using 3.3.2
Reopening to try to mark as verified.
resolving as fixed.
verified
closing - now issue appears as verified.