i'm fine with moving my code from mojo to maven... when I wrote failsafe I was not an apache committer...
I'd like to sort out scoping toolchains before doing that though so I was thinking 2.6 could be the merged version I'd plan on pushing 2.6 in a month or so (i.e. before m3) -Stephen 2010/1/2 Arnaud HERITIER <[email protected]>: > And what about the failsafe plugin > This one is very useful and is a copy of surefire dedicated to its with > junit. > Couldn't we move it to Apache and use a shared lib to update them all > together ? > Couldn't we integrate it by default in maven 3 in the lifecycle ? > > WDYT ? > > Arnaud Héritier > Software Factory Manager > eXo platform - http://www.exoplatform.com > --- > http://www.aheritier.net > > > On Sat, Jan 2, 2010 at 12:47 PM, Stephen Connolly < > [email protected]> wrote: > >> Here is the test plan. >> >> 1. We (=benjamin) run all the builds that are currently working with >> m3+plugin-enfocer+new surefire plugin -SNAPHOT. If all builds still >> pass with the new surefire plugin, then we say all is good >> >> 2. If all is good, we (=benjamin or me or somebody else) stage a >> release of maven-surefire plugin. >> >> 3. We (=benjamin) run all the builds that are currently working with >> m3+plugin-enfocer+new surefire plugin (staged release). If all builds >> still pass with the new surefire plugin, then we say all is good and >> call a vote >> >> Any body got any objections / additional test cases to add? >> >> I have deployed updated 2.5-SNAPSHOT, Step 1 has been started already. >> If anyone has any issues they are willing to fix this week, scream >> now (in the next 24h) and I will hold off until Friday before starting >> step 2. >> >> -Stephen >> >> --------------------------------------------------------------------- >> 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]
