Return-Path: 
 <ant-dev-return-21626-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@apache.org
Received: (qmail 63260 invoked from network); 19 Dec 2001 22:40:08 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 19 Dec 2001 22:40:08 -0000
Received: (qmail 28289 invoked by uid 97); 19 Dec 2001 22:40:12 -0000
Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org
Received: (qmail 28278 invoked by uid 97); 19 Dec 2001 22:40:11 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-dev-help@jakarta.apache.org>
List-Post: <mailto:ant-dev@jakarta.apache.org>
List-Id: "Ant Developers List" <ant-dev.jakarta.apache.org>
Reply-To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 20640 invoked from network); 19 Dec 2001 22:27:37 -0000
X-Authentication-Warning: homer.gst.com: chris set sender to blunck@gst.com
 using -f
Subject: Manifest.java class - Question on length field
From: Christopher Blunck <blunck@gst.com>
To: ant-dev@jakarta.apache.org, blunck@gst.com
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/1.0 (Preview Release)
Date: 19 Dec 2001 17:27:36 -0500
Message-Id: <1008800856.11626.4.camel@homer.gst.com>
Mime-Version: 1.0
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hello-

I'm using jakarta-ant-1.4.1 and I noticed that in
org.apache.tools.ant.taskdefs.Manifest that the MAX_LINE_LENGTH is set
to 70.  I'm wondering why that number was chosen.  Here is why...

I'm building a J2EE application using Ant as my build and assembly
tool.  I have dependancies amongst my EJB components and (as such) I'm
using the Class-Path: feature in the MANIFEST.MF of each EJB JAR to
declare those dependancies.  

To accomplish this, I've written a dependancy.mf file in each of my
component's META-INF directory.  After weblogic.ejbc finishes converting
my JAR to an EBJ JAR, I update the MANIFEST.MF file with the includes
from my dependancy.mf file like this:

<jar jarfile="${build.dir}/jar/ejb-${bean.name}.jar"
     update="true"
     manifest="${bean.src.dir}/META-INF/dependancy.mf"/>


Here is a snapshot of one of the dependancy.mf files (note the long
line):
Class-Path:     echo-core.jar ejb-userprofile.jar
ejb-providerprofile.jar ejb-property.jar

(Apologies if my email client has mangled this line, but all the entries
are on the same line and there is a carriage return at the end of the
line).


When the JAR task in ant completes the re-jar'ing of my EJB, the
output'ed MANIFEST.MF file looks like this:
Class-Path:     echo-core.jar ejb-userprofile.jar  ejb-prov
 iderprofile.jar ejb-property.jar


I may have screwed up the splicing of ejb-providerprofile.jar, but I'm
sure you all get the point ;-). 

WebLogic obviously can't correctly deploy this EJB because the
Class-Path line is incomplete or incorrect. (Whatever you want to call
it).

I made a change to your Manifest.java file and made the MAX_LINE_LENGTH
300 (instead of 70) and the Class-Path line was correctly generated. 
But I'm still left wondering why it was set to 70 to begin with...




-c


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