ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Lynch <billj...@gmail.com>
Subject Re: FW: Multiple Class-Path entries in Manifiest task
Date Thu, 02 Dec 2004 17:03:03 GMT
Here's some sample code for what Conor suggests:

        <fileset dir="${lib.dir}" id="lib.files">
            <include name="**/*.jar"/>
        </fileset>
        <pathconvert pathsep=" " dirsep="/" property="libfiles"
refid="lib.files">
            <map
from="${basedir}${file.separator}build${file.separator}" to=""/>
        </pathconvert>

Then use the ${libfiles} prop.

We just ran into this too.

Cheers,
--Bill

On Thu, 02 Dec 2004 21:42:44 +1100, Conor MacNeill <conor@apache.org> wrote:
> Victor Ionescu wrote:
> >
> > Class-Path: bsh-1.3.0.jar commons-digester.jar commons-collections.jar
> >
> > because:
> > 1) It's more flexible
> > 2) It conforms to the jar specification
> >
> > Question: What's the reason behind this multi Class-Path feature?
> >
> 
> The reasons are specified in this bug report
> http://issues.apache.org/bugzilla/show_bug.cgi?id=4683
> 
> Two Sun specifications, both of which remain current are in conflict and
> we need to support the multiple Class-Path mode.
> 
> If you want to avoid the warning, create a path and use PathConvert to
> create a single Class-Path entry.
> 
> Conor
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
> 
>

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


Mime
View raw message