ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastien BLANC <Sebastien.Bl...@alcatel.com>
Subject Re: manifest task / wrapping after 72 bytes
Date Fri, 22 Nov 2002 00:59:51 GMT
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:
> > <manifest file="${thispkg.dir}/META-INF/MANIFEST.MF" mode="update">
> > <attribute name="classpath" value="global-jar-tl1-types.jar
> > global-jar-gem-types.jar ejb-jar-gm3-types.jar"/>
> > <manifest>
> > <manifest file="${thispkg.dir}/META-INF/MANIFEST.MF" mode="update">
> > <attribute name="classpath" value="global-jar-tl1-types.jar
> > global-jar-gem-types.jar ejb-jar-gm3-types.jar"/>
> > <manifest>
> > <manifest file="${thispkg.dir}/META-INF/MANIFEST.MF" mode="update">
> > <attribute name="classpath" value="global-jar-tl1-types.jar
> > global-jar-gem-types.jar ejb-jar-gm3-types.jar"/>
> > <manifest>
> > 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:
> > > > <manifest file="${thispkg.dir}/META-INF/MANIFEST.MF"
> > mode="update">
> > > >     <attribute name="classpath" value="global-jar-tl1-types.jar
> > > > global-jar-gem-types.jar ejb-jar-gm3-types.jar"/>
> > > > </manifest>
> > > > 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 <manifest> 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:
> <mailto:ant-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> <mailto:ant-user-help@jakarta.apache.org>
>
> --
> To unsubscribe, e-mail:
> <mailto:ant-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:ant-user-help@jakarta.apache.org>
>
> --
> To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>


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


Mime
View raw message