ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <ddevie...@gmail.com>
Subject Re: Manifest Classpath ( programmatically generated but messedup).
Date Mon, 22 Jun 2009 19:47:35 GMT
On Mon, Jun 22, 2009 at 11:58 AM, Garima Bathla<garima.bathla@gmail.com> wrote:
> That exactly is what  I am doing, using Ant's Manifest class. Problem
> happens to be that my classpath is too big and Manifest file has limit of 72
> characters per line, so even though it spits out my configured classpath ,
> it ain't set correctly (as I have listed in the orginial thread).
>
> Any help is highly appreciated, it must not be this tricky to set long
> classpaths programmatically?

Manifest can break a CP longer than 72 char on several lines correctly,
using the proper rules, and has been doing it correctly for years.

Very few bugs reported against it turned out to be real bugs in fact.
So I strongly suggest you take a second look, assuming it does the
correct thing. Note though that line breaks is only the beginning.

The Class-Path: attribute also needs to use the proper file and path separators,
be absolute or relative to the jar, and for this you should depend on
ManifestClasspath,
another Ant class that can take a Path and again format it correctly. --DD

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message