Hello
I noticed a change of behaviour in Maven 3.4, which made one of our builds
fail.
It may be a bit of a corner case, so I'll let someone else decide whether
it's a regression or a bug fix...
We have a submodule where the "parent" pom contains a dependency with
scope=import, but with the version set using a property:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.alfresco</groupId>
<artifactId>alfresco-platform-distribution</artifactId>
<version>${alfresco.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
In the submodule itself, we override this version to be a more recent one:
<properties>
<alfresco.version>5.1.e</alfresco.version>
</properties>
In Maven 3.3 and before, the override is working, and we inherit version
5.1.e of the dependencies.
In maven 3.4, it doesn't any more, so we get older versions of the
dependencies.
It works fine if I move the property override to the parent pom, i.e. the
one where the import dependency is defined.
I've just retested using the latest 3.4.0-SNAPSHOT from 2016-08-06
Thanks for your insight
--
Samuel
--
View this message in context:
http://maven.40175.n5.nabble.com/Preleminary-Maven-3-4-0-SNAPSHOT-Testing-Take-3-tp5874456p5877660.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
