Hi, Siarhei is right about the difference regarding the two goals of the plugin. I know the deploy target works (tested with JBoss 4.2.2), so you must be missing something. Is the right port specified? Is JBoss started? There is some info here: http://bill.burkecentral.com/2008/02/13/jboss-unit-testing-with-maven/ Niether Bill or I could get the start target to work though. I spent some time trying to debug, but I just could figure out the problem. So what I've done is that I use the cargo plugin for starting/stopping JBoss.
Hope it helps, /Anders Ricky-22 wrote: > > could be. I am going to dig and just as an FYI let you know. Thanks and > appreciate your response! > > Rick > > On Wed, Aug 13, 2008 at 6:34 PM, Siarhei Dudzin > <[EMAIL PROTECTED]>wrote: > >> On Thu, Aug 14, 2008 at 12:18 AM, Ricky <[EMAIL PROTECTED]> wrote: >> >> > Hi, >> > >> > Thanks for your reply. I used jboss:harddeploy and it worked for me. >> > However >> > i see that jboss:start doesnt actually start the server. Am i missing >> > something? >> >> >> I never used jboss plugin so I can't tell why it doesn't start. >> >> >> > and also jboss:deploy vs hard deploy whats the difference? >> >> >> No idea, but I can imagine is that jboss:deploy is deployment via jmx >> deployer and hard deploy is just dropping the artifact to the hot >> deployment >> directory of jboss. >> >> Siarhei >> > > -- View this message in context: http://www.nabble.com/Deploying-war-to-JBOSS-using-maven-tp18968835p18982637.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
