You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Stefan Arentz <st...@gmail.com> on 2006/06/02 15:00:58 UTC
Re: [M2] Problem deploying with maven 2 and Ant
On 5/30/06, Roland Asmann <Ro...@cfc.at> wrote:
> Or just forget about the ant-part and use the jboss-maven-plugin! (See also this thread: Unable to locate local repo in Mac-OSX(how to call ant from maven))
>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>jboss-maven-plugin</artifactId>
> <configuration>
> <jbossHome>/path/to/jboss</jbossHome>
> </configuration>
> </plugin>
>
> And then run one of its goals (deploy / harddeploy)
I'm using this plugin too. It kind of works. What I really don't like
is that I have to do a mvn install in my project's top level directory
and then a jboss:deploy in the ear module directory. Is there any way
around that?
S.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [M2] Problem deploying with maven 2 and Ant
Posted by Roland Asmann <Ro...@cfc.at>.
Bind it to a certain phase in your ear so that it gets run automatically, eg:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jboss-maven-plugin</artifactId>
<inherited>true</inherited>
<configuration>
<jbossHome>${appserver.home}</jbossHome>
</configuration>
<executions>
<execution>
<id>deploy</id>
<phase>verify</phase>
<goals>
<goal>harddeploy</goal>
</goals>
</execution>
</executions>
</plugin>
Roland
On Friday 02 June 2006 15:00, Stefan Arentz wrote:
> On 5/30/06, Roland Asmann <Ro...@cfc.at> wrote:
> > Or just forget about the ant-part and use the jboss-maven-plugin! (See
> > also this thread: Unable to locate local repo in Mac-OSX(how to call ant
> > from maven))
> >
> > <plugin>
> > <groupId>org.codehaus.mojo</groupId>
> > <artifactId>jboss-maven-plugin</artifactId>
> > <configuration>
> > <jbossHome>/path/to/jboss</jbossHome>
> > </configuration>
> > </plugin>
> >
> > And then run one of its goals (deploy / harddeploy)
>
> I'm using this plugin too. It kind of works. What I really don't like
> is that I have to do a mvn install in my project's top level directory
> and then a jboss:deploy in the ear module directory. Is there any way
> around that?
>
> S.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org