Here's some sample code for what Conor suggests:
Then use the ${libfiles} prop.
We just ran into this too.
Cheers,
--Bill
On Thu, 02 Dec 2004 21:42:44 +1100, Conor MacNeill <[EMAIL PROTECTED]> wrote:
> Victor Ionescu 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.ap
Hi,
I use the manifest task and I have multiple Class-Path entries:
I get a warning:
"Multiple Class-Path attributes are supported but violate the Jar specification
and may not be correctly processed in all environments"
The generated manifest will have
