Page Comparison

...

If you need to pass additional arguments e.g. for code signing this is possible like this:

mvn -DargumentsDargLine="-Dgpg.keyname=XXX-Dgpg.passphraseServerId=XXX" gitflow:release

...

• skipTestProject=true: Same behavior as jgitflow-maven-plugin. Additionally this prevents build failures in case you have never built the project locally and your modules have dependencies to each other. By default gitflow-maven-plugin executes a hard-coded “mvn clean test” without an install (this does also not change when setting installProject to true).

• pushRemote=false: Do not automatically push develop/master branches and the tag - if anything goes wrong you can easily drop the changes locally.

• verbose=true: Show the maven build that is executed during the release process - important if you have lengthy builds.

• commitMessagePrefix: Is prepended to every commit message automatically generated by the plugin.

• postReleaseGoals: Make sure the artifacts are deployed to the maven repository during the release .Special execution definition: This is a workaround to make sure the Maven profile and the release-profile is used for the release. See #231 for details gets activated.

Another important point for projects which have separate aggregator and parent POMs (as it is usual for wcm.io-based projects): We had to enable the “processAllModules” flag for the versions-maven-plugin to ensure the versions of the child modules are updated as well (see this config section).

...