What is parent version range syntax that works with 3.4? Or you are saying parent version ranges are not supported at all now?
-- Regards, Igor On Fri, Nov 18, 2016, at 10:57 PM, Christian Schulte wrote: > Am 11/19/16 um 03:58 schrieb Igor Fedorenko: > > Thank you for the analysis of the IT failures, Christian. I have a few > > questions/observations, if you don't mind > > > > MavenITmng2199ParentVersionRangeTest.testValidLocalParentVersionRange > > From what I can tell, module uses parent version=[1.0,2) which matches > > locally available parent version=1.1. Can you explain why this test is > > expected to fail? > > Put another way: You cannot deploy this module > <https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=blob;f=core-it-suite/src/test/resources/mng-2199-parent-version-range/local-parent/module/pom.xml;h=85769ce5af3a46f57ff4f15bb3faa366278d4cec;hb=b015e1cf9860fa9f3725a4393d7a0dc8a0868b2f> > to a repository without a version. There is no way to add a dependency > to this module. What version would you put into that dependency? The > corresponding validation was missing in the core only for local parents. > For parents resolved from repositories that module would never have > worked. Just download Maven 3.2.2, remove that parent pom from disc and > try building that module standalone. It will fail with an error message > stating the version must be a constant as well. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
