[ANN] Apache Maven Surefire Plugin 2.17 Released

2014-03-16 Thread Andreas Gudian
The Apache Maven team is pleased to announce the release of the Apache Maven Surefire Plugin, version 2.17 This release comes with some smaller improvements and bug fixes for TestNG, for the JUnit Parallel Computer, the removal of temporary files, and last but not least it fixes a compatibility

Re: MRELEASE-431

2014-03-16 Thread Robert Scholte
Hi Chris, the input is a String, so it's possible to support as many digits as you can. However, an ArtifactVersion [1] doesn't support that much digits, so I'll lock it to 3 to keep the current Maven versioning style. When working with ranges 1.0.0.10 comes before 1.0.0.9 because the part

Re: MRELEASE-431

2014-03-16 Thread Robert Scholte
Hi Chris, This is already the default behavior[1]. No reason to change it, just have to move it to the DefaultVersionPolicy. Robert [1] http://maven.apache.org/maven-release/maven-release-manager/xref/org/apache/maven/shared/release/versions/DefaultVersionInfo.html Op Sun, 16 Mar 2014

RFC: maven-enforcer-rule: http://jira.codehaus.org/browse/MENFORCER-186

2014-03-16 Thread Karl Heinz Marbaise
Hi, i have created a new rule which checks the reactor of a multi-module build if the versions within the reactor are all the same and if the parents use the same version as well Furthermore if dependencies reference artifacts from the current reactor (may be with a wrong version)

Re: RFC: maven-enforcer-rule: http://jira.codehaus.org/browse/MENFORCER-186

2014-03-16 Thread Mirko Friedenhagen
RequireReactorProjectsHaveUniqueVersion? Regards Mirko -- Sent from my mobile On Mar 16, 2014 2:47 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi, i have created a new rule which checks the reactor of a multi-module build if the versions within the reactor are all the same and if the

Re: RFC: maven-enforcer-rule: http://jira.codehaus.org/browse/MENFORCER-186

2014-03-16 Thread Michael Osipov
Am 2014-03-16 14:52, schrieb Mirko Friedenhagen: RequireReactorProjectsHaveUniqueVersion? This does not imply that they have the same version but only unique. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For

Re: RFC: maven-enforcer-rule: http://jira.codehaus.org/browse/MENFORCER-186

2014-03-16 Thread Karl Heinz Marbaise
Hi, Am 2014-03-16 14:52, schrieb Mirko Friedenhagen: RequireReactorProjectsHaveUniqueVersion? This does not imply that they have the same version but only unique. Hm..that's my thoughts as well...apart from that we use the term unique in relationship with SNAPSHOT's and timestamped

Re: RFC: maven-enforcer-rule: http://jira.codehaus.org/browse/MENFORCER-186

2014-03-16 Thread Mirko Friedenhagen
+1 Regards Mirko -- Sent from my mobile On Mar 16, 2014 4:30 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi, Am 2014-03-16 14:52, schrieb Mirko Friedenhagen: RequireReactorProjectsHaveUniqueVersion? This does not imply that they have the same version but only unique. Hm..that's

MJAVADOC-388

2014-03-16 Thread Benson Margulies
Vincent, could you perhaps have a look here before I take a leap at a fix? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: MRELEASE-431

2014-03-16 Thread Chris Graham
I've been using the 4 digit versions with the release plugin for the last 6 years or so. I've never used ranges, as I either thought there was a problem with them and the release plugin. So if 1.0.0.10 comes before 1.0.0.9, wouldn't 1.0.10 therefor come before 1.0.9? -Chris On Sun, Mar 16, 2014

Re: MRELEASE-431

2014-03-16 Thread Paul Benedict
I think everything after the third digit becomes a lexographic compare. That is why three behavior is unexpected to you. This is not an issue with the standard three numbers. On Mar 16, 2014 7:39 PM, Chris Graham chrisgw...@gmail.com wrote: I've been using the 4 digit versions with the release