Nope. bind the execution to the install phase in a profile and then use * http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#releaseProfilesto activate the profile on release perform *
On 10 August 2010 16:07, Sergio Oliveira <[email protected]> wrote: > Problem is NOT switching 'deploy' to 'install'. A <goals>install</goals> > will do it. > > Problem IS cascading an exec:exec after release:perform. You can try and > you > will see that's NOT possible. Probably something related to the fact that > release:perform forks another maven process. Even mvn release:perform > exec:exec does not work. > > Depending on the profile, I would like to release:perform to generate a war > from SVN tag and exec:exec to deploy remotely using a shell script. The > profile will determine which deploy shell script will be executed. The one > for QA or the one for PRODUCTION. > > My workaround so far for this maven annoyance is to force the user to call > twice: > > mvn release:perform > > mvn exec:exec -P qa > > It would have been much better to be able to do: > > mvn release:perform -P qa > > But that is IMPOSSIBLE with maven. > > -Sergio > > On Tue, Aug 10, 2010 at 1:50 AM, Stephen Connolly < > [email protected]> wrote: > > > Have a look at * > > > > > http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#releaseProfiles > > * > > > > 2010/8/10 Martin Schayna <[email protected]> > > > > > I am using this configuration for firing goal 'install' instead of > > 'deploy' > > > in 'release:perform': > > > > > > <build> > > > ... > > > <plugins> > > > ... > > > > > > <plugin> > > > <artifactId>maven-release-plugin</artifactId> > > > <version>2.0-beta-9</version> > > > <configuration> > > > <autoVersionSubmodules>true</autoVersionSubmodules> > > > <goals>install</goals> > > > <useReleaseProfile>false</useReleaseProfile> > > > </configuration> > > > </plugin> > > > </plugins> > > > </build> > > > > > > M. > > > > > > > > > > > > On 08/10/2010 06:38 AM, Sergio Oliveira wrote: > > > > > >> I change goals from release:perform to install instead of the default > > >> deploy. > > >> > > >> But maven ignores my profile 'release' for phase 'install'. It works > > when > > >> I > > >> call mvn install -P release. But not when I call mvn release:perform > -P > > >> release. > > >> > > >> It gives the beautiful: Profile with id: 'release' has not been > > activated. > > >> > > >> Any ideas why maven makes it so trivial? > > >> > > >> > > >> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > >
