have a look at the release profile... but beware the old adage: less haste, more speed
i.e. In trying to make this short-cut you could make much more work for you than the short cut removes... This is akin to those fools who try to only run the unit tests once when they are using a code coverage tool and miss the tests that are broken when instrumented to measure code coverage. Depending on what your preparation goals are you could have issues. I'd favour aborted releases than risking bad releases (i.e. change your preparation goals from "clean verify" to "clean") as at least that way you've tagged the release and the tests are being run on the code checked out from the tag... With your approach you could have code that passed the preparation goals but when checked out from the tag does not build because of SCM issues. With the short preparation goals, only artifacts that can build from the tag will be deployed to your remote repository... (but maybe not all of the tag will build) -Stephen 2009/3/16 Christian Hammers <[email protected]> > Hello > > I've learned to do "mvn release:prepare && mvn release:perform" to do a > release. > > Apparently though both steps perform a "mvn test" which takes quite a > time in one of my projects so I would like to eleminate the redundant > second test pass. > > Is it possible to do something like "mvn release" which automatically does > both steps in a more clever way or is there something I can write in the > pom.xml to disable the unit testing only in the release:perform but of > course > not in the release:prepare stage? > > bye, > > -christian- > > -- > NETCOLOGNE Gesellschaft für Telekommunikation mbH > Am Coloneum 9 | 50829 Köln > Tel: 0221 2222-8711 | Fax: 0221 2222-78711 > > www.netcologne.de > > Geschäftsführer: > Werner Hanf > Karl-Heinz Zankel > HRG 25580, AG Köln > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
