...
If you have no special configuration for jgitflow-maven-plugin
in your project POMs you have nothing to do besides updating to the latest version of global-parent
(33 35 or higher) or aem-global-parent
(1.4.10 16 or higher).
If you have multiple releasable modules within a single GIT repository and a configuration like this in place that customizes the branch and tag names:
...
If this is not sufficient for you there is a these GitHub issue may help: #232, #235.
Details of the gitflow-maven-plugin configuration
In the wcm.io global-parent
/aem-global-parent
the gitflow-maven-plugin
is configured ready-to-use to behave as similar as possible as the jgitflow-maven-plugin
, see the corresponding configuration section in global-parent POM and the default settings.
Some remarks on the configuration parameters we’ve chosen:
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 defaultgitflow-maven-plugin
executes a hard-coded “mvn clean test” without an install (this does also not change when setting installProject to true).verbose=true: Show the maven build that is executed during the release process - important if you have lengthy builds.
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 pluginversionsForceUpdate=true: Make sure all child modules are updated as well.
postReleaseGoals: Make sure the artifacts are deployed to the maven repository during the release and the
release-profile
gets activated.
...
commitMessagePrefix: Is prepended to every commit message automatically generated by the plugin.
If you do not use the global-parent
POM: Please make also sure you have updated to the latest version of versions-maven-plugin
to ensure the versions of the child modules are updated as well (see this config section (2.8.1 or later).
Related articles
Filter by label (Content by label) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...