Thanks, this seems to be what I was looking for. On Tue, Aug 10, 2010 at 1:35 PM, Larry Shatzer, Jr. <lar...@gmail.com>wrote:
> I've seen it like this in a parent corporate pom: > > In the release plugin configuration: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-release-plugin</artifactId> > <configuration> > <preparationGoals>clean install</preparationGoals> > <goals>deploy -P release</goals> > </configuration> > </plugin> > > Then later on: > > <profile> > <!-- Used only when invoking release:perform so as not to re-run > tests as part of the deployment--> > <id>release</id> > <properties> > <skipTests>true</skipTests> > </properties> > </profile> > > On Tue, Aug 10, 2010 at 11:25 AM, C. Benson Manica <cbman...@gmail.com> > wrote: > > I do pretty much always want to release with the tests done, but why do > they > > have to run twice for essentially the same process, i.e. prepare and > > perform? They take a long time, and are they really likely to fail > between > > prepare and perform? I guess if I'm stuck, I'm stuck, but this seems > > gratuitous. > > > > On Tue, Aug 10, 2010 at 12:40 PM, Tony Chemit <che...@codelutin.com> > wrote: > > > >> Le Tue, 10 Aug 2010 12:32:55 -0400, > >> "C. Benson Manica" <cbman...@gmail.com> a écrit : > >> > >> > mvn -DskipTests=true -Dmaven.test.skip=true release:perform still > insists > >> on > >> > running the unit tests. Why? They already ran on release:prepare, I > >> > really, really, really get annoyed sitting through five minutes of > unit > >> > tests that I know pass because I just ran them. > >> > > >> > >> When doing a mvn release:perform, the plugin just launch another > instance > >> of maven with by default this command : > >> > >> mvn deploy site-deploy -DperformRelease > >> > >> So you will never be able to change this behaviour like you are trying > to > >> do. > >> > >> To make this possible you can use one of the release:perform parameter. > >> > >> Before shouting after maven, just try to understand it :) and have a > look > >> to the documentation. > >> > >> In your case, this the page [0] > >> > >> What your are doing seems not natural to me, one of my best-pratice is > to > >> ALWAYS release with tests done, otherwise, the generated ste (and the > >> surefire report) will say : no tests passed, is it really what you want > ? > >> > >> [0] > http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html > >> > >> > >> -- > >> Tony Chemit > >> -------------------- > >> tél: +33 (0) 2 40 50 29 28 > >> email: che...@codelutin.com > >> http://www.codelutin.com > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > > > > > -- > > C. Benson Manica > > cbman...@gmail.com > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- C. Benson Manica cbman...@gmail.com
