Hi, You're writing "remote jboss server"; is the jboss instance on a remote server? If that's the case, cargo cannot start/stop it, that can only be done on a local instance. (However, your current script binds to localhost, so maybe your saying 'remote' out of a Maven instance jvm perspective?)
It's my opinion that cargo is the best choice as it gives you a unified interface, independent of app server. However, there is also a JBoss AS specific plugin: http://mojo.codehaus.org/jboss-maven-plugin/ In the past, I've used a mix of these two plugins to get things rocking (that was before v1.0 of cargo). /Anders On Wed, Jul 15, 2009 at 00:20, daniel.green<october...@gmail.com> wrote: > > I would like to configure my build scripts to deploy an ear file to a remote > jboss server. However, as a requirement, I also need the ability to start > the server, from the script, with parameters. > > Our current Perl and Bash scripts start the server with the following > arguments: > > <code> > --configuration="..." -b localhost -Djboss.jndi.conf.root="..." > -Djboss.jndi.conf.specific="..." > </code> > > Is it possible to replicate this behavior through maven and > jboss-maven-plugin? Or am I stuck with Perl and Bash for now? > > -- > View this message in context: > http://www.nabble.com/Passing-Variables-at-JBoss-Startup-tp24488807p24488807.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
