github
/
winsw
mirror of https://github.com/winsw/winsw
1
0
Fork 0
Code Issues Releases Wiki Activity

Update Developer documentation for Maven Packaging

pull/332/head
Oleg Nenashev 2019-08-19 18:17:36 +02:00 committed by GitHub
parent 2edf74f2c0
commit 7e427aaf4c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
DEVELOPER.md
View File

@ -46,10 +46,5 @@ Then deploy changes to _GitHub Releases_ and NuGet using the available publisher
### Releasing to the Maven repository (legacy) ### Releasing to the Maven repository (legacy)
Maven repository is no longer the main source of releases, Maven repository is no longer the main source of releases,
but WinSW can be deployed there on-demand. but some projects still depend on WinSW from the Jenkins Maven repository.
Some projects (e.g. [Jenkins](https://jenkins.io)) still depend on WinSW from the Maven repository. Maven Packaging repository can be found [here](https://github.com/jenkinsci/winsw-maven-packaging).
1. Make sure you have passed the Release steps above
2. Modify the `winsw.version` property to the the release version (`WINSW_VERSION`)
3. Modify version field to `${WINSW_VERSION}-SNAPSHOT`
4. Run `mvn release:prepare release:perform`