e1fabfc4a2
The top level project here now is spring-cloud-build and any library in Spring Cloud should try and use it as a parent to avoid duplicate plugin and build declarations. The new module here is spring-cloud-dependencies-parent and all BOMs in Spring Cloud should use this as a parent (for the same reason). All sub-projects in Spring Cloud should have a BOM, and if they want to (usually they do) they can use it to define dependencies by importing it into their parent. User's apps should use the spring-cloud-*-dependencies if they need a BOM (because they do *not* have spring-boot-* as a parent). Then they can choose a version of Spring Boot more easily (by choosing a version of spring-boot-starter-parent).
// Do not edit this file (e.g. go instead to src/main/asciidoc) Spring Cloud Build is a common utility project for Spring Cloud to use for plugin and dependency management. == Building and Deploying To install locally: ---- $ mvn install ---- and to deploy snapshots to repo.spring.io: ---- $ mvn deploy -DaltSnapshotDeploymentRepository=repo.spring.io::default::https://repo.spring.io/libs-snapshot-local ---- for a RELEASE build use ---- $ mvn deploy -DaltReleaseDeploymentRepository=repo.spring.io::default::https://repo.spring.io/libs-release-local ---- and for jcenter use ---- $ mvn deploy -DaltReleaseDeploymentRepository=bintray::default::https://api.bintray.com/maven/spring/jars/org.springframework.cloud:build ---- and for Maven Central use ---- $ mvn deploy -P central -DaltReleaseDeploymentRepository=sonatype-nexus-staging::default::https://oss.sonatype.org/service/local/staging/deploy/maven2 ---- (the "central" profile is available for all projects in Spring Cloud and it sets up the gpg jar signing, and the repository has to be specified separately for this project because it is a parent of the starter parent which users in turn have as their own parent).