manifest task / wrapping after 72 bytes
sblanc Nov 21, 2002 8:55 PMHello !
I'm using jboss-3.0.4. Could you look at the following ANT forward. The exception thrown at deployment time is the following:
2002-11-21 17:01:58,661 INFO [org.jboss.ejb.EjbModule] Started
2002-11-21 17:01:58,661 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/Data/jboss-3.0.4/server/ems/deploy/ejb-jar-ems-ems.jar
2002-11-21 17:01:58,661 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
Incompletely deployed packages:
[org.jboss.deployment.DeploymentInfo@fda8b4b4 { url=file:/C:/Data/jboss-3.0.4/server/ems/deploy/gem.ear }
deployer: org.jboss.deployment.EARDeployer@766806
status: Deployment FAILED reason: Could not create deployment: file:/C:/Data/jboss-3.0.4/server/ems/tmp/deploy/server/ems/deploy/gem.ear/77.gem.ear-contents/ejb-jar-gem-SigTable.jar; - nested throwable: (java.lang.NoClassDefFoundError: com/alcatel/gem/ejb/gem/Domain/interfaces/DomainManager)
state: FAILED
watch: file:/C:/Data/jboss-3.0.4/server/ems/deploy/gem.ear
lastDeployed: 1037918223501
lastModified: 1037918222390
mbeans:
]MBeans waiting for classes:
is this a bug on ur side ?
thanx.
seb.
Subject:
Re: manifest task / wrapping after 72 bytes
Date:
Thu, 21 Nov 2002 18:59:51 -0600
From:
Sebastien BLANC <Sebastien.Blanc@alcatel.com>
Reply-To:
"Ant Users List" <ant-user@jakarta.apache.org>
Organization:
Alcatel USA
To:
Ant Users List <ant-user@jakarta.apache.org>
References:
1
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:
> <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>