You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "AO Industries, Inc. (Jira)" <ji...@apache.org> on 2021/11/28 16:01:00 UTC
[jira] [Updated] (MJAVADOC-682) Reactor builds fail when multiple modules with same groupId:artifactId
[ https://issues.apache.org/jira/browse/MJAVADOC-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
AO Industries, Inc. updated MJAVADOC-682:
-----------------------------------------
Description:
In versions 3.1.0 through 3.3.1, 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 effect.
* We believe this to be distinct from [Issue #673|https://issues.apache.org/jira/projects/MJAVADOC/issues/MJAVADOC-673]
was:
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 effect.
* We believe this to be distinct from [Issue #673|https://issues.apache.org/jira/projects/MJAVADOC/issues/MJAVADOC-673]
> 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, 3.3.1
> 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.1, 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 effect.
> * 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.20.1#820001)