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 25694 - Class-Path: in manifest causes java.io.Exception
Summary: Class-Path: in manifest causes java.io.Exception
Status: CLOSED INVALID
Alias: None
Product: platform
Classification: Unclassified
Component: Module System (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-16 16:04 UTC by Dana Kaufman
Modified: 2008-12-23 08:32 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Manifest file with Class Path: that is too long? (1.13 KB, text/plain)
2002-07-16 16:06 UTC, Dana Kaufman 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dana Kaufman 2002-07-16 16:04:08 UTC 
We have split our module into several jar files and 
include them in our modules manifest file using the 
ClassPath: item.  We just added a new jar reference in the 
manifest and are now getting the following error when the 
module is loaded:

Tue Jul 16 11:13:07 EDT 2002: java.io.IOException: line 
too long
java.io.IOException: line too long
        at java.util.jar.Attributes.read
(Attributes.java:336)
        at java.util.jar.Manifest.read(Manifest.java:161)
        at java.util.jar.Manifest.<init>(Manifest.java:56)
        at java.util.jar.JarFile.getManifest
(JarFile.java:145)
        at org.netbeans.core.modules.Module.loadManifest
(Module.java:348)
        at org.netbeans.core.modules.Module.<init>
(Module.java:112)
        at org.netbeans.core.modules.ModuleManager.create
(ModuleManager.java:273)
        at org.netbeans.core.modules.ModuleList$1.run
(ModuleList.java:341)
        at 
org.openide.filesystems.EventControl.runAtomicAction
(EventControl.java:89)
        at 
org.openide.filesystems.FileSystem.runAtomicAction
(FileSystem.java:388)
        at org.netbeans.core.modules.ModuleList.readInitial
(ModuleList.java:250)
        at org.netbeans.core.modules.ModuleSystem.readList
(ModuleSystem.java:224)
        at org.netbeans.core.NonGui.run(NonGui.java:518)
        at org.netbeans.core.Main.run(Main.java:213)
        at org.openide.TopManager.initializeTopManager
(TopManager.java:120)
        at org.openide.TopManager.getDefault
(TopManager.java:81)
        at org.netbeans.core.Main.main(Main.java:346)
        at org.netbeans.core.TopThreadGroup.run
(TopThreadGroup.java:87)
[catch] at java.lang.Thread.run(Thread.java:484)
Comment 1 Dana Kaufman 2002-07-16 16:06:14 UTC 
Created attachment 6729 [details]
Manifest file with Class Path: that is too long?
Comment 2 Petr Nejedly 2002-07-16 16:50:54 UTC 
Lines in manifest have to be wrapped, Manifest will unwrap them
while parsing. We can't do anything about it from inside NetBeans.
Comment 3 Jesse Glick 2002-07-16 17:01:28 UTC 
Did you try line-wrapping your manifest at or before 72 columns as
required by the manifest specification? I think it works.

http://developer.java.sun.com/developer/bugParade/bugs/4620323.html
http://developer.java.sun.com/developer/bugParade/bugs/4295946.html
Comment 4 Quality Engineering 2003-07-01 15:56:41 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified.
Comment 5 Quality Engineering 2003-07-01 16:45:55 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.