Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 47587 invoked from network); 22 Nov 2002 01:00:45 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 22 Nov 2002 01:00:45 -0000 Received: (qmail 26215 invoked by uid 97); 22 Nov 2002 01:01:44 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 26199 invoked by uid 97); 22 Nov 2002 01:01:43 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 26186 invoked by uid 98); 22 Nov 2002 01:01:43 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3DDD8187.33C78D85@alcatel.com> Date: Thu, 21 Nov 2002 18:59:51 -0600 From: Sebastien BLANC Organization: Alcatel USA X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Ant Users List Subject: Re: manifest task / wrapping after 72 bytes References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I'm working with JBOSS and all the depencies that are on the wrapped lines (2nd or more) throw exceptions at deployment time saying that my bean depend on these jar files - as if they were not here. I'll check on jboss email list. thanx. seb. "Karr, David" wrote: > The important point is that wrapped lines in the manifest are perfectly > fine. The code that reads the manifest expects that possibility and > deals with it properly. You don't have to do anything to "fix" it. > > > -----Original Message----- > > From: Sebastien BLANC [mailto:Sebastien.Blanc@alcatel.com] > > > > Hello Connor ! > > u mean the task supports multiple arguments ? do u have an > > example coz I'm not > > sure wat u mean ? > > or do u mean that java allows u to put > > classpath: jarfile1 > > classpath: jarfile2 ? > > > > I've tried the following: > > > > > > > > > > > > > > > > > > > > and the classpath attribute is replaced by the value only of > > the latest > > manifest task. > > > > ? > > > > seb. > > > > Conor MacNeill wrote: > > > > > Sebastien BLANC wrote: > > > > Hello ! > > > > I'm using the manifest task to insert jar file references into the > > > > classpath attribute of my MANIFEST. > > > > I currently only have 3 jar files in the classpath value > > and it already > > > > does go over 72 bytes: > > > > > mode="update"> > > > > > > > > > > > > I know the 72 limit is based on one of the java RFC yet I > > wonder what is > > > > the solution ? > > > > 1. put one jar file per line ? do u know if it will work ? > > > > 2. if this does work, then could ant split after the space in the > > > > attribute value before the 72 limit and not just after > > this 72 limit coz > > > > currently I get something like > > > > classpath: global-jar-tl1-types.jar > > global-jar-gem-types.jar ejb-jar-g > > > > [line break] m3-types.jar > > > > thanx for help. > > > > Sebastien. > > > > > > > > > > The element will accept multiple class-path > > entries. This is > > > the only attribute which supports this behaviour. What > > problem is the > > > splitting causing you. It should still work without any issues. > > > > > > Conor > > > > > > -- > > > To unsubscribe, e-mail: > > > For additional commands, e-mail: > > > -- > To unsubscribe, e-mail: > > For additional commands, e-mail: > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: