For example, when data flow server local inherits from the dataflow parent pom we get
[DEBUG] org.eclipse.aether:aether-transport-http:jar:1.0.2.v20150114:compile
[DEBUG] org.apache.httpcomponents:httpclient:jar:4.5:compile (version managed from 4.2.6 by org.springframework.cloud:spring-cloud-consul-dependencies:1.1.1.RELEASE)
coming from spring-cloud camden bom
but if after changing data flow local server to inherti from the sprint boot parent pom, we get a different version
[DEBUG] org.eclipse.aether:aether-transport-http:jar:1.0.2.v20150114:compile
[DEBUG] org.apache.httpcomponents:httpclient:jar:4.5.2:compile (version managed from 4.2.6 by org.springframework.boot:spring-boot-dependencies:1.4.1.RELEASE)
This means that the other projects in spring-cloud-dataflow that inherit from the data flow parent pom are getting slightly different versions. See the diff below.
However, adding spring-boot-dependency bom before the spring-cloud-dependency bom in the spirng-cloud-dataflow parent pom
For example, when data flow server local inherits from the dataflow parent pom we get
coming from spring-cloud camden bom
but if after changing data flow local server to inherti from the sprint boot parent pom, we get a different version
This means that the other projects in spring-cloud-dataflow that inherit from the data flow parent pom are getting slightly different versions. See the diff below.
However, adding spring-boot-dependency bom before the spring-cloud-dependency bom in the spirng-cloud-dataflow parent pom
brings the versions in sync (I only checked httpclient version).
Should we add this to the parent pom?
Here is a full diff