[Result] [Vote] [Take 2] Release Maven Surefire 2.3.1

Mauro Talevi wrote: Hi all, all showstoppers have been addressed. Second attempt for Maven Surefire 2.3.1 release. Issues solved: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&styleName=Html&version=13251 Staging repo: http://people.apache.org/~mauro/staging-repo/ Tag

Re: defining goals that aggregate other maven goals

On 19/12/2007, Pete Aykroyd <[EMAIL PROTECTED]> wrote: > > Yeah, I've been running into that... but wasn't aware that it was expected > behavior. Thanks for the heads up. > I've searched around and have found some earlier discussions where maven > developers made it clear that this was the way that

RE: defining goals that aggregate other maven goals

It effectively means that every plugin needs to be a wrapper around another shared module so that other things can use the code. It certainly works, but is more overhead than should optimally be required. -Original Message- From: Pete Aykroyd [mailto:[EMAIL PROTECTED] Sent: Tuesday, Decem

Re: defining goals that aggregate other maven goals

Yeah, I've been running into that... but wasn't aware that it was expected behavior. Thanks for the heads up. I've searched around and have found some earlier discussions where maven developers made it clear that this was the way that maven was to be used. I can't figure out a way to make this kind

Add a new dry-run mode to DefaultLifecycleExecutor (was : how to bypass dependency resolution ?)

For those who didn't follow my provious post, the issue is about IDE-support plugins that require a previously-built project to setup the dev environment. When the source code is broken, you have to fix it under VI / notepad. I experimented Kenney Westerhof

Re: [Vote] [Take 2] Release Maven Surefire 2.3.1

On Dec 15, 2007 7:39 PM, Mauro Talevi <[EMAIL PROTECTED]> wrote: > Hi all, > > all showstoppers have been addressed. Second attempt for Maven Surefire > 2.3.1 release. > > Issues solved: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&styleName=Html&version=13251 > > Staging rep

Re: Merging shitty-maven-plugin and maven-invoker-plugin was [Re: [MECLIPSE] refactor IT tests to use shitty maven plugin ?]

On 17 Dec 07, at 12:17 AM 17 Dec 07, olivier lamy wrote: Hi, Agree on merge but in a new plugin or merging in maven-invoker- plugin ? Before starting this work, I'd like to release the current maven-invoker-plugin to not delay some other releases which depends on this. I will call a vote