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.
Summary: | JarDataObject eagerly open the jar file | ||
---|---|---|---|
Product: | java | Reporter: | Petr Nejedly <pnejedly> |
Component: | Unsupported | Assignee: | Jan Pokorsky <jpokorsky> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | issues |
Priority: | P2 | Keywords: | PERFORMANCE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Petr Nejedly
2006-08-28 14:15:27 UTC
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 |