On Fri Jul 04 01:52, Florian Grandel wrote: > jh_manifest may produce a MANIFEST.MF that does not conform to the jar > specification. See http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html. > > The following problems may occur: > > Blank lines are significant. They separate sections within the manifest. > Certain attributes must be included in the main section (e.g. Class-Path, > Main-Class), others are individual attributes and must be included in an > independent section (e.g. Debian-Java-Home), otherwise they will be > ignored or wrongly parsed (see my entry to the debian-java mailing list). > jh_manifest does not separate main section and individual section > attributes.
Why should Debian-Java-Home not be in the main section? it applies to the jar as a whole? Yes, I should fix the parsing and blank line handling > Lines may not be longer than 72 bytes. If they are longer they must be > wrapped. The continuation line must start with a space. jh_manifest does > not wrap long lines. This is especially important when converting > $CLASSPATH to Class-Path: ... as the user doesn't have the possibility > to influence this process from outside. Lines that are correctly wrapped > in xyz.manifest will not be correctly copied to the target MANIFEST.MF. I definitely need to fix this > Nice to have: It would be nice if line endings were consistently handled. > This is not required by the spec but it makes viewing/editing the > MANIFEST.MF easier. I propose automatically converting all CR or CRLF > to (unix-style) LF. > Sure, why not. I'll try and upload a new version today Thanks, Matt -- Matthew Johnson
signature.asc
Description: Digital signature
