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.
J have many jars/zips randomly placed in my $HOME (bad habit of not setting FireFox's download dir). Some of them are even corrupted. The IDE chokes on them randomly, e.g. because of the favorites view, so I traced the opening of them (beyond the scheduled refresh in RP). Here it goes: org.netbeans.core.startup.layers.ArchiveURLMapper.getFileObjects(ArchiveURLMapper.java:110) org.openide.filesystems.URLMapper.findFileObject(URLMapper.java:188) org.openide.filesystems.FileUtil.getArchiveRoot(FileUtil.java:1226) org.netbeans.modules.java.jarloader.JarDataNode.childrenFor(JarDataNode.java:50) org.netbeans.modules.java.jarloader.JarDataNode.<init>(JarDataNode.java:37) org.netbeans.modules.java.jarloader.JarDataObject.createNodeDelegate(JarDataObject.java:43) org.openide.loaders.DataObject$1.run(DataObject.java:253) org.openide.util.Mutex.readAccess(Mutex.java:293) org.openide.loaders.DataObject.getNodeDelegate(DataObject.java:249) org.openide.loaders.DataObject.getClonedNodeDelegate(DataObject.java:274) org.openide.loaders.FolderChildren.createNodes(FolderChildren.java:143) Basically, JarDataNode opens the Jar file immediatelly in its ctor, which is very unpolite. Imagine I had many, maybe large .zip files in some folder, they'd all get opened as soon as I merely browse into the folder.
Note: Even commit validation fails for me because of such files in my $HOME, which is pretty bad.
That's true, it is not much wise. I will fix it. However I have not idea how it relates to commit validation tests.
> However I have not idea how it relates to commit validation tests. It's just a coincidence that during testModuleInstallation, there is a refresh performed and during that refresh, exception is logged: org.openide.filesystems.FSException: Error in JAR file /space/nenik/broken.zip: invalid CEN header (bad signature) at org.openide.filesystems.FSException.io(FSException.java:88) at org.openide.filesystems.JarFileSystem.setJarFile(JarFileSystem.java:246) and the infrastructure probably considers any logged exception during that test as a showstopper.
fixed in /cvs/java/src/org/netbeans/modules/java/jarloader/JarDataNode.java,v <-- JarDataNode.java new revision: 1.3; previous revision: 1.2