You're describing Maven's default behavior. Perhaps you have configured surefire or Maven to react differently to a test failure.
Justin On Apr 12, 2010, at 7:58 AM, Henika Tekwani <[email protected]> wrote: > > Thanks for such a prompt response. > > I don't have much idea about how the staging feature of nexus works. > I will > have to understand first. > > But I wanted to know that is there a way that we can configure our > deploy > plugin such that it deploys only when the tests that were run in > test phase > pass with 100%? > I mean that based on the outcome of the tests can we control the > execution > of the other build phases? > > So my case is that > > Stephen Connolly-2 wrote: >> >> Use nexus and staged deployment then you can do it in one go. >> >> The artifacts produced in one maven execution are no longer in the >> reactor >> when you run a second time. >> >> Staged deployment is what you want, then you just do mvn deploy... >> run >> your >> tests of the artifacts and either drop the staged deployment or >> promote >> it... >> >> If you cannot get the purchase of pro-Nexus, then you can do poor >> man's >> staging with wagon-maven-plugin... or you can wait until staging is >> required >> by me and I scratch my own itch and write an OSS plugin to provide >> staging >> in Nexus Open Source ;-) >> >> -Stephen >> >> P.S. I do NOT work for Sonatype, but I like and use Nexus. >> >> On 12 April 2010 10:52, Henika Tekwani <[email protected]> wrote: >> >>> >>> Hi All, >>> >>> Basically what I am trying to achieve is to break the default build >>> lifecycle into two parts: >>> >>> 1. mvn install. >>> 2. mvn deploy:deploy. >>> >>> The first step runs fine. But when I run "mvn deploy:deploy" it >>> gives the >>> following error: >>> >>> [INFO] [deploy:deploy {execution: default-cli}] >>> [INFO] >>> --- >>> --- >>> ------------------------------------------------------------------ >>> [ERROR] BUILD ERROR >>> [INFO] >>> --- >>> --- >>> ------------------------------------------------------------------ >>> [INFO] The packaging for this project did not assign a file to the >>> build >>> artifact >>> >>> What am I doing wrong? >>> >>> Please note that when I run "mvn deploy" on my project it >>> successfully >>> deploys my project's jar file. >>> >>> -- >>> View this message in context: >>> http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28215706.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] >>> >>> >> >> > > -- > View this message in context: > http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28216800.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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
