[gatein-dev] Jboss51 deployment with cargo-1.0.3 ?

[Matt Wringe]

On Tue, 2010-09-28 at 10:22 -0400, Matt Wringe wrote:
> On Tue, 2010-09-28 at 09:48 +0200, Alain DEFRANCE wrote:
> > Hi Matt,
> > 
> > After integration of your patch, the dependency problem still exists (logs joined)
> > I can commit my working version but it's probably the the same code as you.
> 
> Oops, I made the change and saw that the build completed without looking
> at the results. Its an issue with how jboss unit is setup. The JBoss 5.x
> deployers were drastically changed between cargo 1.0.2 and 1.0.3 and it
> broke some backwards compatibility (and I don't know why they didn't
> release it as 1.1.0).

Yeah, it looks like the Cargo 1.0.3 changes are going to be a problem.
Is there anything in 1.0.3 that we need or can we use 1.0.2 for a while?

> > Alain.
> > 
> > 
> > Le 27 sept. 2010 à 18:43, Matt Wringe a écrit :
> > 
> > > On Wed, 2010-09-22 at 10:09 -0400, Matt Wringe wrote:
> > >> On Wed, 2010-09-22 at 15:30 +0200, Alain DEFRANCE wrote:
> > >>> Hi Matt,
> > >>> 
> > >>> 
> > >>> I currently work with Julien Viet on WCI to deploy him on tomcat7.
> > >>> I've changed the cargo version from 1.0.1-alpha2 to 1.0.3 (tomcat7
> > >>> support + bugfix).
> > >>> Since the 1.0.3 version (In the 1.0.2 version it's work fine), cargo
> > >>> can't deploy on jboss51.
> > >> 
> > >> If it worked on 1.0.2 but not 1.0.3 then it sounds like a bug :(
> > >> 
> > >>> 
> > >>> According to this documentation http://cargo.codehaus.org/JBoss+Remote
> > >>> +Deployer, I'd added the 2 dependencies
> > >>> cargo-core-tools-jboss-deployer-5.1-and-onwards
> > >>> and jboss-profileservice-spi.
> > > 
> > > you just need to add those dependencies to the ant plugin for it to
> > > work. Attached is a patch which will apply to your branch that will do
> > > this. Its a bit confusing as we are using maven to call ant, so the
> > > extra step is needed.
> > > 
> > >>> Some classes still cannot be found (for
> > >>> instance : org.jboss.aop.proxy.MarshalledInterfaceProxy).
> > >> 
> > >> Since its a missing org.jboss.* class and not an org.codehaus.cargo.*
> > >> class, it looks like it was based on a different version of JBoss AS.
> > >> 
> > >>> 
> > >>> You can look that
> > >>> here : http://anonsvn.jboss.org/repos/gatein/components/wci/branches/adf/
> > >>> 
> > >> 
> > >> I havn't worked on cargo for a while, but I do know my way around it. I
> > >> will take a look the next time I have a bit of free time. You might also
> > >> try asking on the cargo users mailing list (not sure how active it is
> > >> lately).
> > >> 
> > >>> It is a bug in cargo or missing other dependencies ?
> > >> 
> > >> It hard to tell if its a bug or if its a configuration issues. I don't
> > >> think its an issue with missing dependencies, if that was the case it
> > >> shouldn't be missing org.jboss classes.
> > >> 
> > >>> 
> > >>> Regards.
> > >>> Alain Defrance.
> > >>> _______________________________________________
> > >>> gatein-dev mailing list
> > >>> gatein-dev at lists.jboss.org
> > >>> https://lists.jboss.org/mailman/listinfo/gatein-dev
> > >> 
> > >> 
> > >> _______________________________________________
> > >> gatein-dev mailing list
> > >> gatein-dev at lists.jboss.org
> > >> https://lists.jboss.org/mailman/listinfo/gatein-dev
> > > 
> > > <cargo-remote-deployment.patch>
> > 
> 
> 
> _______________________________________________
> gatein-dev mailing list
> gatein-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev