Hi,
I use the manifest task and I have multiple Class-Path entries:
<manifest>
<attribute name="Built-By" value="${user.name}"/>
<attribute name="Class-Path" value="bsh-1.3.0.jar"/>
<attribute name="Class-Path" value="commons-digester.jar"/>
<attribute name="Class-Path" value="commons-collections.jar"/>
</manifest>
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 three Class-Path entries:
Class-Path: bsh-1.3.0.jar
Class-Path: commons-digester.jar
Class-Path: commons-collections.jar
I think it would be best not to get the warning and instead to generate a
single Class-Path entry:
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?
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.791 / Virus Database: 535 - Release Date: 11/8/2004
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.791 / Virus Database: 535 - Release Date: 11/8/2004
