Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.1.0, 3.1.1, 3.2.0, 3.3.0, 3.3.1, 3.3.2, 3.4.0, 3.4.1, 3.5.0, 3.6.0, 3.6.2
-
Debian Linux versions 10.10 through 12.2
OpenJDK 64-bit versions 11.0.11 through 17.0.9
Maven versions 3.8.1 through 3.9.5
Description
In versions 3.1.0 through 3.6.2, 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 —
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
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
Attachments
Issue Links
- links to