More documentation required

[marcelstoer]

There are few things I don't understand about this plugin which I find no answers for in the documentation.

• I assume the plugin invokes the Maven deploy phase & plugin at the end of the release process just like the traditional plugin does?
• The SSH & HTTPS authentication configurations are explained quite nicely at http://danielflower.github.io/multi-module-maven-release-plugin/usage.html#Authentication. However, AFAICS it doesn't say anywhere if the configuration is for authenticating against the Git repository or against the deployment endpoint (e.g. Nexus). What if these two remote locations need different authentication schemes?
• How does the plugin determine if it should release not? Put differently for which events will it create a new release?
• How does the plugin determine the next build number? What information sources does it analyze e.g. Git local & remote tags, Maven locale & repo content, others?
• There is this message " [WARNING] No changes have been detected in any modules so will re-release them all" that's a bit irritating as it seems to contradict one of the fundamental propositions of the plugin which is

only those modules that have changes should be released

[Romain125]

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.

[marcelstoer]

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

[mtwig]

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.