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.

Bug 175330 - java.io.IOException: invalid header field
Summary: java.io.IOException: invalid header field
Status: RESOLVED INCOMPLETE
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: rmichalsky
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-23 19:14 UTC by sheff
Modified: 2009-10-23 21:12 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 135868


Attachments
stacktrace (1.85 KB, text/plain)
2009-10-23 19:14 UTC, sheff
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sheff 2009-10-23 19:14:10 UTC
Build: NetBeans IDE 6.8 Beta (Build 200910212001)
VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Windows XP, 5.1, x86

User Comments:
GUEST: Estava carregando a IDE

GUEST: Adicionando bibliotecas

GUEST: Abrindo Projeto



Stacktrace: 
java.io.IOException: invalid header field
        at java.util.jar.Attributes.read(Attributes.java:393)
        at java.util.jar.Manifest.read(Manifest.java:182)
        at java.util.jar.Manifest.<init>(Manifest.java:52)
        at org.netbeans.modules.apisupport.project.ManifestManager.getInstance(ManifestManager.java:160)
        at org.netbeans.modules.apisupport.project.universe.ModuleList.scanPossibleProject(ModuleList.java:584)
        at org.netbeans.modules.apisupport.project.universe.ModuleList.findOrCreateModuleListFromSuiteWithoutBinaries(ModuleList.java:753)
Comment 1 sheff 2009-10-23 19:14:19 UTC
Created attachment 90013 [details]
stacktrace
Comment 2 Exceptions Reporter 2009-10-23 19:14:24 UTC
This issue already has 6 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=135868
Comment 3 rmichalsky 2009-10-23 21:12:29 UTC
Can someone attach here the jar on which the exception is thrown? When manifest is malformed, there is not much that
apisupport can do. The helpful part would be to find why the manifest is wrong, e.g. in case it is a module jar.
Otherwise I tend to close this as WONTFIX.