There is no such thing as a phase which have been a success. Each plugin can call the build a failure. So if every plugin before that phase didn't call the build a failure it is a success.
For example, you can set the maven-surefire-plugin (which runs your tests) to fail the build on a failed test (this is default, you can change this), you can also bind checkstyle, pmd and others to your verify phase and these can also mark your build as a failure. There is also the option to fail immediately or fail at end or even fail never: mvn options: -ff,--fail-fast Stop at first failure in reactorized builds -fae,--fail-at-end Only fail the build afterwards; allow all non-impacted builds to continue -fn,--fail-never NEVER fail the build, regardless of project result Maybe you can create a plugin, which asks the current build status and act on that information, but I'm not very well at home in the current plugin API. Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, Nov 25, 2008 at 9:56 PM, Durbha, Praveen (GE Healthcare) <[EMAIL PROTECTED]> wrote: > Well, they are ANT tasks to apply a label to Clearcase using the > maven-ant-run-plugin. > > Right now, I have these tasks set up to execute during the "install" > phase of the lifecycle.. > > As this is one of the last few stages of the life cycle, it will execute > only if the prior phases (compile, packaging, etc)have been a > success..correct? > > Thanks > > -----Original Message----- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 25, 2008 11:36 AM > To: Maven Users List > Subject: Re: Question on Maven Build Lifecycle > >> I have ANT tasks configured in my POM file..I would like to have these > >> ANT tasks execute only if my Maven build is successful.. > > What kind of tasks are they? > > What determines a "successful" Maven build -- compiles OK? tests OK? > package creation is OK? installed to local repo cache OK? deployed to > corporate repo OK? If you can answer that question, it will probably > indicate where you should bind the tasks. This is not something we can > answer for you. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
