Release

Relase:

Versioning:

If the branch contains back-portable changes you can perform a revision release changing the Z in X.Y.Z:

geoserver-manager-{major.minor.revision}.jar`

otherwise a minor or major release change is needed. Note that in this case (minor or major release) you have to create a new branch following the branch naming convention as following.

Branch naming convention:

The snapshot release version will follow the branch naming convention. For example if the stable branch name is 1.5.x the development version will be 1.5-SNAPSHOT. The main development branch name will be master (called trunk in SVN) and the resulting maven version will be 1.6-SNAPSHOT.

Note:

For a more detailed discussion on the release process please ref to this page

MVN release plugin:

To release a new version of geoserver manager you can use the mvn release plugin:

The manual way:

The following line will ask you for the new release version:

 mvn release:prepare release:perform -Dall -Dgoals=deploy

It will also deploy the released version before switching to the next snapshot.

Jenkins

 mvn release:prepare release:perform -Dall -Dgoals=deploy  -DdevelopmentVersion=1.6-SNAPSHOT -DreleaseVersion=1.5.5 -Dtag=v1.5.5