SpringCloud/spring-cloud-release-tools
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Ensuring that release versions don't use snapshot versions

Browse Source 
without this change we could commit a release version that references a dependency in a snapshot version
with this change an exception will be throw in such a case. Exception will contain a file name together with the line in which a snapshot version was found

fixes #7
This commit is contained in:
Marcin Grzejszczak
2017-03-13 15:35:32 +01:00
parent 0a18deff11
commit 037a5e4e0a
22 changed files with 969 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/src/main/asciidoc/spring-cloud-release-tools.adoc
View File

@@ -17,7 +17,9 @@ why this tool makes it easy to automate the release / dependency update process
- Clones the Spring Cloud Release project and picks all versions (Boot + Cloud projects)
- Modifies the project versions with values from SC-Release
- Performs the build and checks if the `docs` modules have properly created the documentation (no `unresolved` tags are present)
* throws an exception when we bump versions to release and there's a SNAPSHOT version referenced in the POM
- Performs the build and checks if the `docs` modules have properly created the documentation
* throws an exception when in the `docs` module there's an unresolved tag in any HTML file
- Commits changed poms (ONLY FOR NON-SNAPSHOT VERSIONS)
- Creates a tag for the release / milestone (ONLY FOR NON-SNAPSHOT VERSIONS)
- Runs the deployment of the artifacts