[
https://issues.apache.org/jira/browse/MJAVADOC-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17373101#comment-17373101
]
AO Industries, Inc. edited comment on MJAVADOC-682 at 7/1/21, 11:23 PM:
------------------------------------------------------------------------
Multiple projects of the same groupId:artifactId, but with different versions,
are an important part of our workflow. We support multiple branches of many of
our projects, and we have all projects in a giant Git submodule + Maven module
hierarchy. This allows us to perform aggregate tasks across all 984 projects
at once, such as testing, analyzing dependencies, auditing ossindex
vulnerabilities, deploying, publishing to Tomcats, ...
Any loss of this capability would definitely increase our workload and decrease
the utility of Maven.
was (Author: aoindustries):
Multiple projects of the same groupId:artifactId, but with different versions,
are an important part of our workflow. We support multiple branches of many of
our projects, and we have all projects in a giant Git submodule + Maven module
hierarchy. This allows us to perform aggregate tasks across all 984 projects
at once, such as testing, analyzing dependencies, deploying, publishing to
Tomcats, ...
Any loss of this capability would definitely increase our workload and decrease
the utility of Maven.
> Reactor builds fail when multiple modules with same groupId:artifactId
> ----------------------------------------------------------------------
>
> Key: MJAVADOC-682
> URL: https://issues.apache.org/jira/browse/MJAVADOC-682
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar, javadoc
> Affects Versions: 3.1.0, 3.1.1, 3.2.0, 3.3.0
> Environment: Debian Linux 10.10, Java 11.0.11, Maven 3.8.1
> Reporter: AO Industries, Inc.
> Priority: Major
>
> In versions 3.1.0 through 3.3.0, when a reactor build has multiple projects
> with the same groupId and artifactId, even when different versions, the
> javadoc fails with:
> Exit code: 1 - error: module not found: com.aoindustries.example
> Plugin 3.0.1 works.
> We have created a minimal example project that demonstrates this bug:
> [https://github.com/aoindustries/maven-javadoc-plugin-failing-multiple-projects-same-name]
>
> --- Copy from demo project README.md ---
> h2. To Reproduce:
> # Clone this project: {{git clone
> [https://github.com/aoindustries/maven-javadoc-plugin-failing-multiple-projects-same-name.git]}}
> # Change to project directory: {{cd
> maven-javadoc-plugin-failing-multiple-projects-same-name}}
> # Perform build to see error in {{jar}} goal: {{mvn verify}}
> # Also fails with {{javadoc}} goal: {{mvn clean compile javadoc:javadoc}}
> h2. Notes:
> * Can build individual modules directly, such as {{(cd module-1 && mvn
> verify)}}
> * Reverting to maven-javadoc-plugin version 3.0.1 makes it work
> * Changing the groupId or artifactId in either module-1 or module-2 makes it
> work.
> * Changing module names, package names, or class names in modules has no
> affect.
> * We believe this to be distinct from [Issue
> #673|https://issues.apache.org/jira/projects/MJAVADOC/issues/MJAVADOC-673]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
