More documentation required about multi-module-maven-release-plugin HOT 3 OPEN

Hi,
Concerning you last point, you can use the noChangeAction parameter and set it to ReleaseNone.
Agreed that it is a bit disturbing though...should be set to "ReleaseNone" as a default value.

from multi-module-maven-release-plugin.

Yep, that's what we've done in the meantime.

from multi-module-maven-release-plugin.

I would also benefit from additional documentation on what exactly makes something considered different.
I have two identical projects, one built locally, another building from a Jenkins server.
Changes in the local version work as expected, with each module getting versioned independently. On the Jenkins version, every module is considered changed every time.
The project structure is:

• root
  • greeting
    • greeting-api
    • greeting-service (depends on greeting-api)
    • greeting-cli (depends on greeting-service)
  • bom

There is no obvious/significant difference between the two projects.

from multi-module-maven-release-plugin.