Hi Robert,
> I wonder if this does what we want to achieve: forcing projects using
maven-shared-utils to be executed with at least Maven 2.2.1.
Right now it is just the preferred version, no problem if the project
itself redefines it to 2.0.9 for instance.
Is that a problem or should we say [2.2.1,) ?
Well spotted...The problem with this property is that this will be used
for an artifact dependency maven-toolchain as well...
Apart from that it had been on 2.1.0 before....
So i think it's best to separate these to things...
So defining an version range might be not the best idea...in my
opinion...or only for prerequisites...which is ok...
I have made a change you might take a look on it and say if you are fine
with it...or not...
Kind regards
Karl-Heinz Marbaise
thanks,
Robert
Op Sat, 27 Sep 2014 22:30:03 +0200 schreef <[email protected]>:
Author: khmarbaise
Date: Sat Sep 27 20:30:03 2014
New Revision: 1628003
URL: http://svn.apache.org/r1628003
Log:
[MSHARED-359]
- Upgrade to Maven 2.2.1 build and compatibility.
Modified:
maven/shared/trunk/maven-shared-utils/pom.xml
Modified: maven/shared/trunk/maven-shared-utils/pom.xml
URL:
http://svn.apache.org/viewvc/maven/shared/trunk/maven-shared-utils/pom.xml?rev=1628003&r1=1628002&r2=1628003&view=diff
==============================================================================
--- maven/shared/trunk/maven-shared-utils/pom.xml (original)
+++ maven/shared/trunk/maven-shared-utils/pom.xml Sat Sep 27 20:30:03
2014
@@ -55,7 +55,7 @@
</distributionManagement>
<properties>
- <mavenVersion>2.1.0</mavenVersion>
+ <mavenVersion>2.2.1</mavenVersion>
</properties>
<dependencies>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
