RE: line break in classpath-line in manifest

> From: Daniel Barclay [mailto:[EMAIL PROTECTED]] > > If logical lines are broken across physical lines like RFC 822 header > lines, shouldn't the above line be broken adjacent to some white space? > Not required as I read the jar spec. Conor -- To unsubscribe, e-mail:

RE: line break in classpath-line in manifest

> From: Erik Schalburg [mailto:[EMAIL PROTECTED]] > > Not in my experience. Erik, How did it not work? Did using the jar with a JDK fail? If so how and what version, etc? Conor -- To unsubscribe, e-mail: For additional commands, e-mail:

RE: line break in classpath-line in manifest

> From: Martin Monsorno [mailto:[EMAIL PROTECTED]] > ... > > When building a jar with the jar task, and specifying a manifest-file > which contains a classpath line longer than 72 chars, ant will break > this line at column 72. > ... > Class-Path: crimson.jar some-other.jar log4j.jar jbl.jar

Re: line break in classpath-line in manifest

On 30 Apr 2002 09:34 MDT you wrote: > > When building a jar with the jar task, and specifying a manifest-file > > which contains a classpath line longer than 72 chars, ant will break > > this line at column 72. > > As required by the specification. > Actually, as far as I know it is jar itself

Re: line break in classpath-line in manifest

Martin Monsorno wrote: > When building a jar with the jar task, and specifying a manifest-file > which contains a classpath line longer than 72 chars, ant will break > this line at column 72. As required by the specification. > > Now, does anybody knows, if the resulting classpath line, e.g.

line break in classpath-line in manifest

When building a jar with the jar task, and specifying a manifest-file which contains a classpath line longer than 72 chars, ant will break this line at column 72. Now, does anybody knows, if the resulting classpath line, e.g. Class-Path: crimson.jar some-other.jar log4j.jar jbl.jar blubb.jar xer