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.
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.
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev