Doubt it will make a difference, but you can try -DskipTests=true. Perhaps the alias will have another effect?
On Mon, Jul 19, 2010 at 12:57 AM, Stephen Connolly <[email protected]> wrote: > the reason to bother compiling is to verify that the release build will work > when the version numbers have been transformed. But if you don't mind borked > tags in your SCM.... > > On 19 July 2010 01:26, Zac Thompson <[email protected]> wrote: > >> I think the preparationGoals property could also be useful here >> >> e.g. -DpreparationGoals=clean (if you're not going to test, why bother >> compiling during prepare at all?) >> >> >> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#preparationGoals ->> >> Zac >> >> On Thu, Jul 15, 2010 at 4:57 PM, prenaud76 <[email protected] >> >wrote: >> >> > >> > This sounds very basic, but release:prepare insists on running the test >> > phase >> > although I purposely set the -Dmaven.test.skip=true property. Problem is: >> I >> > don't want to run tests during a release and I cannot seem to find a way >> to >> > skip them. >> > >> > >> > Do you know of a way? >> > >> > >> > (Using the git scm provider) >> > >> > >> > Tx. >> > -- >> > View this message in context: >> > >> http://maven.40175.n5.nabble.com/How-to-skip-tests-during-release-prepare-tp1223821p1223821.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]
