*-start goals don't update version of child modules

[arikkfir]

When running a "-start" goal on a multi-module project (at the root), only the root's version is updated to the new release's version.

[arikkfir]

See pull request #49

[aleksandr-m]

Do you have different group id for the module projects? Can you show relevant parts of your projects pom xmls? Or create a MCVE?

[aleksandr-m]

@arikkfir ^ ping!

[ghost]

One thing to note - versions-maven-plugin added the <processAllModules> property in version 2.5 of that plugin. I've used that in a mixed multi module project where a parent module is used to inherit an external parent POM and most of the modules don't inherit from the root POM. Looks like gitflow uses a hardcoded 2.1 version for the versions:set goal here

gitflow-maven-plugin/src/main/java/com/amashchenko/maven/plugin/gitflow/AbstractGitFlowMojo.java

Line 48 in 228ef8a

private static final String VERSIONS_MAVEN_PLUGIN_SET_GOAL = "org.codehaus.mojo:versions-maven-plugin:2.1:set";

Exposing that behavior via the gitflow might be a simpler solution.