[ 
https://issues.apache.org/jira/browse/MNG-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159004#comment-15159004
 ] 

Stephane Nicoll commented on MNG-5971:
--------------------------------------

{noformat}
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
com.example:demo:jar:0.0.1-SNAPSHOT
[WARNING] Multiple conflicting imports of dependency 
'org.springframework.integration:spring-integration-http:jar' into model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' ('101 : 19, 
org.springframework.integration:spring-integration-bom:4.2.4.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/integration/spring-integration-bom/4.2.4.RELEASE/spring-integration-bom-4.2.4.RELEASE.pom',
 '1803 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom').
 To resolve this conflict, either declare the dependency directly in model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' to override what gets 
imported or rearrange the causing imports in the inheritance hierarchy to apply 
standard override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour. @ 
org.springframework.cloud:spring-cloud-dependencies:Brixton.M5
[WARNING] Multiple conflicting imports of dependency 
'org.apache.httpcomponents:httpclient:jar' into model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' ('103 : 16, 
org.springframework.cloud:spring-cloud-consul-dependencies:1.0.0.M6 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-consul-dependencies/1.0.0.M6/spring-cloud-consul-dependencies-1.0.0.M6.pom',
 '1071 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1071 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1071 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1071 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1071 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom').
 To resolve this conflict, either declare the dependency directly in model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' to override what gets 
imported or rearrange the causing imports in the inheritance hierarchy to apply 
standard override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour. @ 
org.springframework.cloud:spring-cloud-dependencies:Brixton.M5
[WARNING] Multiple conflicting imports of dependency 
'org.apache.httpcomponents:httpcore:jar' into model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' ('108 : 16, 
org.springframework.cloud:spring-cloud-consul-dependencies:1.0.0.M6 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-consul-dependencies/1.0.0.M6/spring-cloud-consul-dependencies-1.0.0.M6.pom',
 '1082 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1082 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1082 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1082 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1082 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom').
 To resolve this conflict, either declare the dependency directly in model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' to override what gets 
imported or rearrange the causing imports in the inheritance hierarchy to apply 
standard override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour. @ 
org.springframework.cloud:spring-cloud-dependencies:Brixton.M5
[WARNING] Multiple conflicting imports of dependency 'joda-time:joda-time:jar' 
into model '[inherited]:spring-cloud-dependencies:pom:Brixton.M5' ('123 : 16, 
org.springframework.cloud:spring-cloud-consul-dependencies:1.0.0.M6 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-consul-dependencies/1.0.0.M6/spring-cloud-consul-dependencies-1.0.0.M6.pom',
 '847 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '847 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '847 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '847 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '847 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom').
 To resolve this conflict, either declare the dependency directly in model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' to override what gets 
imported or rearrange the causing imports in the inheritance hierarchy to apply 
standard override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour. @ 
org.springframework.cloud:spring-cloud-dependencies:Brixton.M5
[WARNING] Multiple conflicting imports of dependency 
'org.springframework:spring-core:jar' into model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' ('29 : 16, 
org.springframework.boot:spring-boot-starter-parent:[unknown-version] 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-starter-parent/1.3.2.RELEASE/spring-boot-starter-parent-1.3.2.RELEASE.pom',
 '1706 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom').
 To resolve this conflict, either declare the dependency directly in model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' to override what gets 
imported or rearrange the causing imports in the inheritance hierarchy to apply 
standard override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour. @ 
org.springframework.cloud:spring-cloud-dependencies:Brixton.M5
[WARNING] Multiple conflicting imports of dependency 
'com.hazelcast:hazelcast:jar' into model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' ('625 : 16, 
org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '64 : 16, org.springframework.cloud:spring-cloud-cluster-dependencies:1.0.0.M4 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-cluster-dependencies/1.0.0.M4/spring-cloud-cluster-dependencies-1.0.0.M4.pom').
 To resolve this conflict, either declare the dependency directly in model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' to override what gets 
imported or rearrange the causing imports in the inheritance hierarchy to apply 
standard override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour. @ 
org.springframework.cloud:spring-cloud-dependencies:Brixton.M5
[WARNING] Multiple conflicting imports of dependency 
'com.hazelcast:hazelcast-spring:jar' into model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' ('635 : 16, 
org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '69 : 16, org.springframework.cloud:spring-cloud-cluster-dependencies:1.0.0.M4 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-cluster-dependencies/1.0.0.M4/spring-cloud-cluster-dependencies-1.0.0.M4.pom').
 To resolve this conflict, either declare the dependency directly in model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' to override what gets 
imported or rearrange the causing imports in the inheritance hierarchy to apply 
standard override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour. @ 
org.springframework.cloud:spring-cloud-dependencies:Brixton.M5
[WARNING] Multiple conflicting imports of dependency 
'org.aspectj:aspectjrt:jar' into model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' ('1163 : 16, 
org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '66 : 16, org.springframework.cloud:spring-cloud-sleuth-dependencies:1.0.0.M5 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-sleuth-dependencies/1.0.0.M5/spring-cloud-sleuth-dependencies-1.0.0.M5.pom').
 To resolve this conflict, either declare the dependency directly in model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' to override what gets 
imported or rearrange the causing imports in the inheritance hierarchy to apply 
standard override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour. @ 
org.springframework.cloud:spring-cloud-dependencies:Brixton.M5
[WARNING] Multiple conflicting imports of dependency 
'org.aspectj:aspectjweaver:jar' into model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' ('1173 : 16, 
org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '71 : 16, org.springframework.cloud:spring-cloud-sleuth-dependencies:1.0.0.M5 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-sleuth-dependencies/1.0.0.M5/spring-cloud-sleuth-dependencies-1.0.0.M5.pom').
 To resolve this conflict, either declare the dependency directly in model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' to override what gets 
imported or rearrange the causing imports in the inheritance hierarchy to apply 
standard override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour. @ 
org.springframework.cloud:spring-cloud-dependencies:Brixton.M5
[WARNING] Multiple conflicting imports of dependency 
'org.apache.curator:curator-recipes:jar' into model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' ('79 : 16, 
org.springframework.cloud:spring-cloud-zookeeper-dependencies:1.0.0.M5 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-zookeeper-dependencies/1.0.0.M5/spring-cloud-zookeeper-dependencies-1.0.0.M5.pom',
 '54 : 16, org.springframework.cloud:spring-cloud-cluster-dependencies:1.0.0.M4 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-cluster-dependencies/1.0.0.M4/spring-cloud-cluster-dependencies-1.0.0.M4.pom').
 To resolve this conflict, either declare the dependency directly in model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' to override what gets 
imported or rearrange the causing imports in the inheritance hierarchy to apply 
standard override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour. @ 
org.springframework.cloud:spring-cloud-dependencies:Brixton.M5
[WARNING] Multiple conflicting imports of dependency 
'org.apache.curator:curator-test:jar' into model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' ('89 : 16, 
org.springframework.cloud:spring-cloud-zookeeper-dependencies:1.0.0.M5 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-zookeeper-dependencies/1.0.0.M5/spring-cloud-zookeeper-dependencies-1.0.0.M5.pom',
 '59 : 16, org.springframework.cloud:spring-cloud-cluster-dependencies:1.0.0.M4 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-cluster-dependencies/1.0.0.M4/spring-cloud-cluster-dependencies-1.0.0.M4.pom').
 To resolve this conflict, either declare the dependency directly in model 
'[inherited]:spring-cloud-dependencies:pom:Brixton.M5' to override what gets 
imported or rearrange the causing imports in the inheritance hierarchy to apply 
standard override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour. @ 
org.springframework.cloud:spring-cloud-dependencies:Brixton.M5
[WARNING] Multiple conflicting imports of dependency 
'org.springframework.integration:spring-integration-http:jar' into model 
'com.example:demo:jar:0.0.1-SNAPSHOT' @ '/Users/snicoll/Downloads/demo 
2/pom.xml' ('101 : 19, 
org.springframework.integration:spring-integration-bom:4.2.4.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/integration/spring-integration-bom/4.2.4.RELEASE/spring-integration-bom-4.2.4.RELEASE.pom',
 '1803 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom').
 To resolve this conflict, either declare the dependency directly in model 
'com.example:demo:jar:0.0.1-SNAPSHOT' to override what gets imported or 
rearrange the causing imports in the inheritance hierarchy to apply standard 
override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour.
[WARNING] Multiple conflicting imports of dependency 
'org.apache.httpcomponents:httpclient:jar' into model 
'com.example:demo:jar:0.0.1-SNAPSHOT' @ '/Users/snicoll/Downloads/demo 
2/pom.xml' ('103 : 16, 
org.springframework.cloud:spring-cloud-consul-dependencies:1.0.0.M6 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-consul-dependencies/1.0.0.M6/spring-cloud-consul-dependencies-1.0.0.M6.pom',
 '1071 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1071 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1071 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1071 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1071 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom').
 To resolve this conflict, either declare the dependency directly in model 
'com.example:demo:jar:0.0.1-SNAPSHOT' to override what gets imported or 
rearrange the causing imports in the inheritance hierarchy to apply standard 
override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour.
[WARNING] Multiple conflicting imports of dependency 
'org.apache.httpcomponents:httpcore:jar' into model 
'com.example:demo:jar:0.0.1-SNAPSHOT' @ '/Users/snicoll/Downloads/demo 
2/pom.xml' ('108 : 16, 
org.springframework.cloud:spring-cloud-consul-dependencies:1.0.0.M6 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-consul-dependencies/1.0.0.M6/spring-cloud-consul-dependencies-1.0.0.M6.pom',
 '1082 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1082 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1082 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1082 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '1082 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom').
 To resolve this conflict, either declare the dependency directly in model 
'com.example:demo:jar:0.0.1-SNAPSHOT' to override what gets imported or 
rearrange the causing imports in the inheritance hierarchy to apply standard 
override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour.
[WARNING] Multiple conflicting imports of dependency 'joda-time:joda-time:jar' 
into model 'com.example:demo:jar:0.0.1-SNAPSHOT' @ 
'/Users/snicoll/Downloads/demo 2/pom.xml' ('123 : 16, 
org.springframework.cloud:spring-cloud-consul-dependencies:1.0.0.M6 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-consul-dependencies/1.0.0.M6/spring-cloud-consul-dependencies-1.0.0.M6.pom',
 '847 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '847 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '847 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '847 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '847 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom').
 To resolve this conflict, either declare the dependency directly in model 
'com.example:demo:jar:0.0.1-SNAPSHOT' to override what gets imported or 
rearrange the causing imports in the inheritance hierarchy to apply standard 
override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour.
[WARNING] Multiple conflicting imports of dependency 
'org.springframework:spring-core:jar' into model 
'com.example:demo:jar:0.0.1-SNAPSHOT' @ '/Users/snicoll/Downloads/demo 
2/pom.xml' ('29 : 16, 
org.springframework.boot:spring-boot-starter-parent:[unknown-version] 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-starter-parent/1.3.2.RELEASE/spring-boot-starter-parent-1.3.2.RELEASE.pom',
 '1706 : 16, org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom').
 To resolve this conflict, either declare the dependency directly in model 
'com.example:demo:jar:0.0.1-SNAPSHOT' to override what gets imported or 
rearrange the causing imports in the inheritance hierarchy to apply standard 
override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour.
[WARNING] Multiple conflicting imports of dependency 
'com.hazelcast:hazelcast:jar' into model 'com.example:demo:jar:0.0.1-SNAPSHOT' 
@ '/Users/snicoll/Downloads/demo 2/pom.xml' ('625 : 16, 
org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '64 : 16, org.springframework.cloud:spring-cloud-cluster-dependencies:1.0.0.M4 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-cluster-dependencies/1.0.0.M4/spring-cloud-cluster-dependencies-1.0.0.M4.pom').
 To resolve this conflict, either declare the dependency directly in model 
'com.example:demo:jar:0.0.1-SNAPSHOT' to override what gets imported or 
rearrange the causing imports in the inheritance hierarchy to apply standard 
override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour.
[WARNING] Multiple conflicting imports of dependency 
'com.hazelcast:hazelcast-spring:jar' into model 
'com.example:demo:jar:0.0.1-SNAPSHOT' @ '/Users/snicoll/Downloads/demo 
2/pom.xml' ('635 : 16, 
org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '69 : 16, org.springframework.cloud:spring-cloud-cluster-dependencies:1.0.0.M4 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-cluster-dependencies/1.0.0.M4/spring-cloud-cluster-dependencies-1.0.0.M4.pom').
 To resolve this conflict, either declare the dependency directly in model 
'com.example:demo:jar:0.0.1-SNAPSHOT' to override what gets imported or 
rearrange the causing imports in the inheritance hierarchy to apply standard 
override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour.
[WARNING] Multiple conflicting imports of dependency 
'org.aspectj:aspectjrt:jar' into model 'com.example:demo:jar:0.0.1-SNAPSHOT' @ 
'/Users/snicoll/Downloads/demo 2/pom.xml' ('1163 : 16, 
org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '66 : 16, org.springframework.cloud:spring-cloud-sleuth-dependencies:1.0.0.M5 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-sleuth-dependencies/1.0.0.M5/spring-cloud-sleuth-dependencies-1.0.0.M5.pom').
 To resolve this conflict, either declare the dependency directly in model 
'com.example:demo:jar:0.0.1-SNAPSHOT' to override what gets imported or 
rearrange the causing imports in the inheritance hierarchy to apply standard 
override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour.
[WARNING] Multiple conflicting imports of dependency 
'org.aspectj:aspectjweaver:jar' into model 
'com.example:demo:jar:0.0.1-SNAPSHOT' @ '/Users/snicoll/Downloads/demo 
2/pom.xml' ('1173 : 16, 
org.springframework.boot:spring-boot-dependencies:1.3.2.RELEASE 
/Users/snicoll/.m2/repository/org/springframework/boot/spring-boot-dependencies/1.3.2.RELEASE/spring-boot-dependencies-1.3.2.RELEASE.pom',
 '71 : 16, org.springframework.cloud:spring-cloud-sleuth-dependencies:1.0.0.M5 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-sleuth-dependencies/1.0.0.M5/spring-cloud-sleuth-dependencies-1.0.0.M5.pom').
 To resolve this conflict, either declare the dependency directly in model 
'com.example:demo:jar:0.0.1-SNAPSHOT' to override what gets imported or 
rearrange the causing imports in the inheritance hierarchy to apply standard 
override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour.
[WARNING] Multiple conflicting imports of dependency 
'org.apache.curator:curator-recipes:jar' into model 
'com.example:demo:jar:0.0.1-SNAPSHOT' @ '/Users/snicoll/Downloads/demo 
2/pom.xml' ('79 : 16, 
org.springframework.cloud:spring-cloud-zookeeper-dependencies:1.0.0.M5 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-zookeeper-dependencies/1.0.0.M5/spring-cloud-zookeeper-dependencies-1.0.0.M5.pom',
 '54 : 16, org.springframework.cloud:spring-cloud-cluster-dependencies:1.0.0.M4 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-cluster-dependencies/1.0.0.M4/spring-cloud-cluster-dependencies-1.0.0.M4.pom').
 To resolve this conflict, either declare the dependency directly in model 
'com.example:demo:jar:0.0.1-SNAPSHOT' to override what gets imported or 
rearrange the causing imports in the inheritance hierarchy to apply standard 
override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour.
[WARNING] Multiple conflicting imports of dependency 
'org.apache.curator:curator-test:jar' into model 
'com.example:demo:jar:0.0.1-SNAPSHOT' @ '/Users/snicoll/Downloads/demo 
2/pom.xml' ('89 : 16, 
org.springframework.cloud:spring-cloud-zookeeper-dependencies:1.0.0.M5 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-zookeeper-dependencies/1.0.0.M5/spring-cloud-zookeeper-dependencies-1.0.0.M5.pom',
 '59 : 16, org.springframework.cloud:spring-cloud-cluster-dependencies:1.0.0.M4 
/Users/snicoll/.m2/repository/org/springframework/cloud/spring-cloud-cluster-dependencies/1.0.0.M4/spring-cloud-cluster-dependencies-1.0.0.M4.pom').
 To resolve this conflict, either declare the dependency directly in model 
'com.example:demo:jar:0.0.1-SNAPSHOT' to override what gets imported or 
rearrange the causing imports in the inheritance hierarchy to apply standard 
override logic. Without resolving this conflict, your build relies on 
indeterministic behaviour.
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING]
{noformat}

This is what I get with the latest bundle FYI

> Imported dependencies should be available to inheritance processing
> -------------------------------------------------------------------
>
>                 Key: MNG-5971
>                 URL: https://issues.apache.org/jira/browse/MNG-5971
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.3.3
>            Reporter: Stephane Nicoll
>            Assignee: Christian Schulte
>            Priority: Trivial
>              Labels: close-pending
>             Fix For: 3.4.0
>
>         Attachments: bom-cloud.zip
>
>
> When a project extends from a parent with a {{dependencyManagement}} section, 
> it is not always possible to properly override (and align) the version to use 
> for a group of dependencies.
> We typically use Bill Of Materials to gather a group of modules and make sure 
> their versions are consistent. 
> The following project demonstrates the issue: 
> https://github.com/snicoll-scratches/maven-dependency-management
> The first commit is a working use case where the parent uses a bom with 
> version A and we use the same bom with version B in the child. Version B is 
> used as expected.
> The second commit demonstrates the faulty scenario. Rather than using a bom 
> in the parent, we use a direct dependency (provided by that bom). We still 
> use the bom with a different version. In that case all the dependencies but 
> the one provided by the parent are overridden (leading to mixed versions for 
> the dependencies provided by the BOM).
> It looks like the distance is still used to compute the version while the 
> graph of dependencies should be flatten at each step for a proper override. 
> Thoughts? Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to