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 that does this, not ant. > > Now, does anybody knows, if the resulting classpath line, e.g. > > > > Class-Path: crimson.jar some-other.jar log4j.jar jbl.jar blubb.jar xerce > > s.jar > > > > will work? > > Yes. Not in my experience. We tried all kinds of different types of manifest files and eventually the only way we could get it to work if the classpath entry was longer than 72 characters was to have each jar on its own line, with spaces padded to the 71st character. Doing that, jar created a classpath entry in the manifest that had correct line breaks. Probably not the right way to handle it, but it worked. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
