Am 11/03/16 um 17:14 schrieb Dave Syer: >> Using current 3.4.0-SNAPSHOT master you can set the model version to >> 4.1.0 and then you can use excludes in the dependency management import. >> Would that solve the issue for you? Could you give that a quick test? > > It's not "a quick test", otherwise I'd be happy to oblige. Or am I missing > something? The whole hierarchy of poms and parents has to be the same model > (seems to be what Maven tells me). It's a really deep hierarchy covering > multiple codebases, not all of which I can or should change. > > Besides, as you say, it's not a practical solution until 4.1.0 is actually > available, and we can impose that constraint on all users.
Could you build a 3.4.0-SNAPSHOT locally for testing not requiring a model version bump? It's easy. You just need to change method 'isGreaterOrEqual' of class 'ModelVersions' to always return 'true'. Just read the whole class below to see what that leads to. You can then test with that 3.4.0-SNAPSHOT without having to change any model version. That's not practical either, I know. I am asking, because it was a Spring developer filing the issues which have lead to the changes. That's the project issues are being reported against now. <https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model-builder/src/main/java/org/apache/maven/model/versioning/ModelVersions.java;h=6b527ca8666c279f55047702b3987f37b032bbe3;hb=HEAD> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
