Am 09/14/16 um 13:50 schrieb Stephane Nicoll: > Well, first of all I have no idea what the following means: > > rearrange the causing imports in the inheritance hierarchy to apply > standard override logic based on artifact coordinates.
Apply inheritance override logic to resolve the conflict. You may need to introduce various parent POMs to be able to do that. For example: Currently you have one POM importing e.g. 3 BOMs introducing conflicts. You can make the one POM a hierarchy of 3 POMs each importing just one of the 3 BOMs. That way a dependency imported into a child dependency management can override the same dependency imported into a parent dependency management. So your former single POM can be used the same way as before (your users need not change anything), but it is composed of various parents now transparently. > "groupId:artifactId:version" coordinates should be enough IMO. And maybe we > could also flip the message so that it is more obvious. Something along the > lines of: > > Dependency 'org.springframework.cloud:spring-cloud-commons:jar' has > conflicting dependency management from ' > org.springframework.cloud:spring-cloud-consul-dependencies:1.0.2.RELEASE' and > 'org.springframework.cloud:spring-cloud-commons-dependencies:1.1.0.RELEASE' > Thanks. Not sure this will be possible when it comes to transitive BOM imports. Will take a look at it. Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
