Am 11/19/16 um 13:35 schrieb Igor Fedorenko: > What is parent version range syntax that works with 3.4? Or you are > saying parent version ranges are not supported at all now?
They got introduced in 3.2.2. This commit <https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=6cf9320942c34bc68205425ab696b1712ace9ba4> about 2 weeks after the release of 3.2.2 broke parent version ranges. They have not been working from there on anymore in any Maven release. This commit <https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=a6aca2894ab5a2849190cb802052710204081bf5> fixes the ITs so that they start detecting parent version ranges are not working. In between there have been commits fixing local parent resolution (readParentLocally). <https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=40d5087b6b134842e2b61a567dbb4bfbcfab7ae6> <https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=25f5143169d39075cee67d9f4d11649cce0fafa0> <https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=bd87258629db8e3fcc7aa04777afc16314c3cde0> When fixing the remote parent resolution (readParentExternally) for 3.4, I noticed the local parent resolution (readParentLocally) is lacking validation. Maven 3.4 will be the first version ever supporting parent version ranges consistently for local and remote parents. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
