https://github.com/spring-cloud/spring-cloud-release

Spring Cloud Release Train - dependency management across a wide range of Spring Cloud projects.
https://github.com/spring-cloud/spring-cloud-release

cloud-native java microservices spring spring-boot spring-cloud spring-cloud-core

Last synced: 13 days ago
JSON representation

Spring Cloud Release Train - dependency management across a wide range of Spring Cloud projects.

• Host: GitHub
• URL: https://github.com/spring-cloud/spring-cloud-release
• Owner: spring-cloud
• License: apache-2.0
• Created: 2014-07-31T19:52:26.000Z (over 10 years ago)
• Default Branch: main
• Last Pushed: 2024-10-11T16:02:41.000Z (about 1 month ago)
• Last Synced: 2024-10-29T16:49:15.186Z (14 days ago)
• Topics: cloud-native, java, microservices, spring, spring-boot, spring-cloud, spring-cloud-core
• Homepage: http://projects.spring.io/spring-cloud
• Size: 3.27 MB
• Stars: 877
• Watchers: 128
• Forks: 180
• Open Issues: 7
• Metadata Files:
  • Readme: README.adoc
  • Contributing: .github/CONTRIBUTING.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

        
////

DO NOT EDIT THIS FILE. IT WAS GENERATED.

Manual changes to this file will be lost when it is generated again.

Edit the files in the src/main/asciidoc/ directory instead.

////

Spring Cloud Release Train is a curated set of dependencies across a

range of Spring Cloud projects. You consume it by using the

spring-cloud-dependencies POM to manage dependencies in Maven or

Gradle. The release trains have names, not versions, to avoid

confusion with the sub-projects. The names are an alphabetic sequence

(so you can sort them chronologically) with names of London Tube

stations ("Angel" is the first release, "Brixton" is the second).

== Generating release train documentation

In order to generate the release train documentation, please update the project with versions for a given release train and then execute the following command:

```bash

$ ./mvnw clean install -Pdocs,train-docs -pl train-docs

```

In order to upload the documentation to the documentation server just execute the following command:

```bash

$ ./mvnw clean deploy -Pdocs,train-docs -pl train-docs

```

IMPORTANT: If you're releasing milestones don't forget to add `-Pmilestone` and if GA `-Pcentral`.

== Contributing

Unresolved directive in  - include::https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/main/docs/src/main/asciidoc/contributing.adoc[]

== Building and Deploying

Since there is no code to compile in the starters they should do not need to compile, but a compiler has to be available because they are built and deployed as JAR artifacts. To install locally:

----

$ mvn install -s .settings.xml

----

and to deploy snapshots to repo.spring.io:

----

$ mvn install -DaltSnapshotDeploymentRepository=repo.spring.io::default::https://repo.spring.io/libs-snapshot-local

----

for a RELEASE build use

----

$ mvn install -DaltReleaseDeploymentRepository=repo.spring.io::default::https://repo.spring.io/libs-release-local

----

and for Maven Central use

----

$ mvn install -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).