I am unable to get jboss to startup correctly due to deployment issues. After digging a little further into the issue, cargo is telling jboss to run the profile it created (from the configure phase) with the exception of the lib directory.
Here is the first part of my log from mvn cargo:run
If you notice, cargo is passing in -Djboss.server.lib.url=file:/home/integ/jboss/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/efault/lib instead of -Djboss.server.lib.url=file:/home/my-proj/test.services/target/cargo/configurations/jboss51x/lib
According to ALL of the documentation that I am reading, you are supposed to place third-party dependency jar files (like jdbc connectors and the like) in <JBOSS_HOME>/server/<CONFIGURATION>/lib. However, cargo is defaulting this value to something that I am unable to change and point to the correct location.