From 7e427aaf4c609f331a69ba531a8e0f091ff9e033 Mon Sep 17 00:00:00 2001 From: Oleg Nenashev Date: Mon, 19 Aug 2019 18:17:36 +0200 Subject: [PATCH] Update Developer documentation for Maven Packaging --- DEVELOPER.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/DEVELOPER.md b/DEVELOPER.md index 79cfd9d..f6595ee 100644 --- a/DEVELOPER.md +++ b/DEVELOPER.md @@ -46,10 +46,5 @@ Then deploy changes to _GitHub Releases_ and NuGet using the available publisher ### Releasing to the Maven repository (legacy) Maven repository is no longer the main source of releases, -but WinSW can be deployed there on-demand. -Some projects (e.g. [Jenkins](https://jenkins.io)) still depend on WinSW from the Maven repository. - -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` \ No newline at end of file +but some projects still depend on WinSW from the Jenkins Maven repository. +Maven Packaging repository can be found [here](https://github.com/jenkinsci/winsw-maven-packaging).