[MJAVADOC-682] Reactor builds fail when multiple modules with same gr…

[michael-o]

…oupId:artifactId, but different versions

Following this checklist to help us incorporate your
contribution quickly and easily:

• Make sure there is a JIRA issue filed
  for the change (usually before you start working on it). Trivial changes like typos do not
  require a JIRA issue. Your pull request should address just this issue, without
  pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
• Format the pull request title like [MJAVADOC-XXX] - Fixes bug in ApproximateQuantiles,
  where you replace MJAVADOC-XXX with the appropriate JIRA issue. Best practice
  is to use the JIRA issue title in the pull request title and in the first line of the
  commit message.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Run mvn clean verify -Prun-its to make sure basic checks pass. A more thorough check will
  be performed on your pull request automatically.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004

• In any other case, please file an Apache Individual Contributor License Agreement.

[ao-apps]

I have created integration tests for MJAVADOC-682: 2f291d4

Should I create a separate pull request, or you can merge this commit into your MJAVADOC-682 branch?

Thank you,

• Dan

[michael-o]

I have created integration tests for MJAVADOC-682: 2f291d4

Should I create a separate pull request, or you can merge this commit into your MJAVADOC-682 branch?

Thank you,

* Dan

I will intergrate from here: https://github.com/ao-apps/maven-javadoc-plugin/tree/MJAVADOC-682

[ao-apps]

Should I change the commit message to begin with "[MJAVADOC-682]"?

[michael-o]

Should I change the commit message to begin with "[MJAVADOC-682]"?

No, I will squash anyway and give you attributions, of course.

[michael-o]

CI is rolling...

[ao-apps]

CI is rolling...

I just noticed a mistake and force-pushed a fix. I left the "package" declaration on top of the module-info.java files.

[michael-o]

CI is rolling...

I just noticed a mistake and force-pushed a fix. I left the "package" declaration on top of the module-info.java files.

Modified...

[ao-apps]

I went ahead and confirmed the provided integration tests for MJAVADOC-682 do, in fact, reproduce the originally reported issue: The build succeeds on 3.0.1 and fails on 3.6.2 as expected.