Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 50931 invoked from network); 29 Sep 2005 15:19:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Sep 2005 15:19:28 -0000 Received: (qmail 55217 invoked by uid 500); 29 Sep 2005 15:19:25 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 55181 invoked by uid 500); 29 Sep 2005 15:19:25 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 55168 invoked by uid 99); 29 Sep 2005 15:19:25 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Sep 2005 08:19:23 -0700 Received: by ajax.apache.org (Postfix, from userid 99) id 812C321C; Thu, 29 Sep 2005 17:19:02 +0200 (CEST) From: bugzilla@apache.org To: dev@ant.apache.org Subject: DO NOT REPLY [Bug 36865] New: - jar task : building a Class-Path X-Bugzilla-Reason: AssignedTo Message-Id: <20050929151902.812C321C@ajax.apache.org> Date: Thu, 29 Sep 2005 17:19:02 +0200 (CEST) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36865 Summary: jar task : building a Class-Path Product: Ant Version: 1.6.5 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Core tasks AssignedTo: dev@ant.apache.org ReportedBy: andy.seaborne@hp.com Trying to set a long Class-Path fails in v1.6.5 ant -version ==> Apache Ant version 1.6.5 compiled on June 2 2005 Case 1/ Inline value (see sample below) This is because class paths in jar manifests are separated by spaces and spaces are also the continuation character in jar manifests. The jar task breaks the long lines so that space may be on the front. Case 2/ Specify an existing manifest file The manifest file has trailing spaces in the Class-Path. The task seems to parse the manifest but then wrap the Class-Path value up without regard to the internal spaces to the value. There is a trick to get spaces into a long Class-Path which is to have trailing spaces in the manifest. This works when running the Java SDK (1.5.0) jar command directly and the same manifest in 2/ used directly works. Manifest-Version: 1.0 Main-Class: arq.query Class-Path: arq.jar jena.jar xercesImpl.jar xml-apis.jar stax-1.1.1-dev.jar stax-api-1.0.jar commons-logging.jar concurrent.jar icu4j.jar jakarta-oro-2.0.5.jar junit.jar (each intermediate line in Class-Path has a trailing space) Samples: lib.jars is set to a string of jars names with spaces -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org