ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26300] - manifest task munges classpath entries
Date Wed, 21 Jan 2004 18:54:48 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26300>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26300

manifest task munges classpath entries





------- Additional Comments From colinml1@exis.com  2004-01-21 18:54 -------
As far as I can tell, Ant's manifest Class-Path wrapping works absolutely fine.
I don't generally use the manifest tag, but even using the jar task with a
manifest attribute to feed it a manifest results in wrapping. If I feed it the
following manifest:
-----
Manifest-Version: 1.0
Class-Path: 
 aopalliance-0.1.jar 
 asm-1.4.jar 
 avalon-framework-4.1.3.jar 
 axis-1.1.jar 
 behaviour_xml.jar 
 ccpp-1.0.jar 
 ccpp-ri-1.0.jar 
 cglib2-1.0.jar 
 classworlds-1.0.jar 
 commons-beanutils-1.6.jar 
 commons-collections-2.1.jar 
 commons-dbcp-1.1.jar 
 commons-digester-1.5.jar 
 commons-lang-1.0.1.jar 
 commons-logging-1.0.3.jar 
 core-services.jar 
 core-util.jar 
 core-dbutil.jar 
 cryptix-3.2.0.jar 
 data-access.jar 
 device-descriptor-xml.jar 
 dom4j-1.3.jar 
 ehcache-0.7.jar 
 glue-std-3.2.3.jar 
 hibernate2-2.1.1.jar 
 jad-manifest-rules-xml.jar 
 jakarta-oro-2.0.8.jar 
 jato-beta5.jar 
 jaxen-1.0-FCS-full.jar 
 jaxp-api-1.2.3.jar 
 jaxrpc-api-1.0.jar 
 jdom-b8.jar 
 jena-1.4.0.jar 
 jstl-1.0.4.jar 
 junit-3.8.1.jar 
 log4j-1.2.8.jar 
 log4j-properties.jar 
 odmg-3.0.jar 
 oscore-tira-1.1.0.jar 
 osuser-tira-1.1.0.jar 
 osuser-tira-jdbc-1.0.0.jar 
 osworkflow-tira-1.1.0.jar 
 packaging.jar 
 png-sixlegs-1.2.3.jar 
 provisioning.jar 
 qa-util.jar 
 quartz-1.0.2.jar 
 rdffilter-1.0.0.jar 
 saaj-1.1.jar 
 saxpath-1.0-fcs.jar 
 spring-1.0M4.jar 
 standard-1.0.4.jar 
 tapestry-3.0-beta-3-post.jar 
 tapestry-contrib-3.0-beta-3-post.jar 
 tira-classfile-1.0.2.jar 
 wsdl4j-20030609.jar 
 xbean-1.0.0.jar 
----- 
Ant then puts the following in the jar file:
-----
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.0
Created-By: 1.4.2_01-b06 (Sun Microsystems Inc.)
Class-Path: aopalliance-0.1.jar asm-1.4.jar avalon-framework-4.1.3.jar
  axis-1.1.jar behaviour_xml.jar ccpp-1.0.jar ccpp-ri-1.0.jar cglib2-1
 .0.jar classworlds-1.0.jar commons-beanutils-1.6.jar commons-collecti
 ons-2.1.jar commons-dbcp-1.1.jar commons-digester-1.5.jar commons-lan
 g-1.0.1.jar commons-logging-1.0.3.jar core-services.jar core-util.jar
  core-dbutil.jar cryptix-3.2.0.jar data-access.jar device-descriptor-
 xml.jar dom4j-1.3.jar ehcache-0.7.jar glue-std-3.2.3.jar hibernate2-2
 .1.1.jar jad-manifest-rules-xml.jar jakarta-oro-2.0.8.jar jato-beta5.
 jar jaxen-1.0-FCS-full.jar jaxp-api-1.2.3.jar jaxrpc-api-1.0.jar jdom
 -b8.jar jena-1.4.0.jar jstl-1.0.4.jar junit-3.8.1.jar log4j-1.2.8.jar
  log4j-properties.jar odmg-3.0.jar oscore-tira-1.1.0.jar osuser-tira-
 1.1.0.jar osuser-tira-jdbc-1.0.0.jar osworkflow-tira-1.1.0.jar packag
 ing.jar png-sixlegs-1.2.3.jar provisioning.jar qa-util.jar quartz-1.0
 .2.jar rdffilter-1.0.0.jar saaj-1.1.jar saxpath-1.0-fcs.jar spring-1.
 0M4.jar standard-1.0.4.jar tapestry-3.0-beta-3-post.jar tapestry-cont
 rib-3.0-beta-3-post.jar tira-classfile-1.0.2.jar wsdl4j-20030609.jar 
 xbean-1.0.0.jar 
-----

And I have had no issues with this in either JDK 1.3.1, JDK 1.4.0, 1.4.1, or 1.4.2.

May I suggest that something else is the problem, maybe line termination, etc?

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


Mime
View raw message