This project manages properties and plugins versions for other projects with

<groupId>pl.kubiczak.felix.shark</groupId>

Project site available at https://shark.kubiczak.pl/

Maven artifacts at http://maven.kubiczak.pl/pl/kubiczak/felix/shark/

mvn release:prepare -B -N -Darguments="-N" -DreleaseVersion=2.1 -DdevelopmentVersion=2.2-SNAPSHOT
mvn release:perform -B -N -Darguments="-N -Dgpg.keyname=01D2F996" -Psign,release 

Submodules of this project are versioned in separate GIT repositories. They are released independently.

mvn release:prepare -B -DreleaseVersion=1.2 -DdevelopmentVersion=1.3-SNAPSHOT 
mvn release:perform -B -Darguments="-Dgpg.keyname=01D2F996" -Psign,release

After all modules are released, please checkout to the release versions commits and execute:

mvn site:site site:deploy

This command will try to find credentials for site deployment in Maven config files i.e.:

<servers>
  <server>
    <id>ftps.server.example.com</id>
    <username>ftp-user-name</username>
    <password>1234567890abcdefghijklmnopqr</password>
    <configuration>
      <endpointChecking>false</endpointChecking>
    </configuration>
  </server>
</servers>

Parent module and submodules are released independently. Therefore during parent module release we need to use -N (non-recursive) flag. This will run Maven Release Plugin for parent module only. We don't want to run release plugin for all submodules at this time.

But as described in Maven Release Plugin FAQ for release plugin we need to use:

mvn -N -Darguments=-N

Release profile adds javadoc and sources artifacts:

-Prelease

sign profile requires gpg2 installed and gpg key id:

-Psign -Dgpg.keyname=9A105524

In order to perform non-interactive release we use:

-B -DreleaseVersion=1.2 -DdevelopmentVersion=1.3-SNAPSHOT

Attribution-NonCommercial 4.0 International

Available Maven plugins upgrades are reported in:

• src/main/resources/plugins-report.txt