Am 11/20/16 um 00:12 schrieb Igor Fedorenko: > Let me rephrase my question. What IT shows how to use parent version > ranges with Maven 3.4?
MNG-2199 <https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=tree;f=core-it-suite/src/test/resources/mng-2199-parent-version-range;hb=HEAD> <https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=blob;f=core-it-suite/src/test/java/org/apache/maven/it/MavenITmng2199ParentVersionRangeTest.java;h=7d77cb720ca27c46a4676faeb6244f46264edeac;hb=HEAD> It's easy. If the <version> in <parent> does not contain a version range, nothing is different. If that element contains a version range, the highest version found will be used and in addition, the project version is no longer allowed to be inherited or to be declared using a property. > We actually use parent version ranges quite extensively internally, so I > am trying to assess the impact of 3.4 changes for our users. You are on a very dangerous road then. The <version> element in <parent> elements has been ignored for all local poms (found using <relativePath>) until <https://issues.apache.org/jira/browse/MNG-5840> got fixed. Last commit for this issue was for Maven 3.3.9. You have not noticed parent version ranges are not working since Maven 3.2.3 for poms read from repositories. Means you are using version ranges in parent elements solely for local poms? They never had been implemented there. You could not notice this, because the <version> in <parent> just got ignored completely. You could have written anything you like into it. This commit <https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=ed5ffbe5afc0be21f750f8cb8c95b6e9a3f3bd0c> fixes an invalid IT. The IT did not test anything due to MNG-5840. You could have left out the <version> in that module's <parent> completely and that IT would have succeeded as well. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
