[
https://issues.apache.org/jira/browse/MJAVADOC-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750502#comment-16750502
]
Robert Scholte commented on MJAVADOC-568:
-----------------------------------------
Even without the parent it fails. Running {{mvn package}} is enough to
reproduce. To awkward thing is that javadoc is generated anyway, so this is
something I need to register this at OpenJDK.
The message looks confusing. What's happening here is that the offline link
(calculated based on project.url in pom) used instead of the folder. The
message is saying that it has found an element-list for module1 (which is true
if you look at that generated javadoc), and that it was expecting that module2
would be documented as module too.
The code now decides based on an existing module descriptor if module-based
documentation should be generated, but this must be based on explicit module
name (respecting the Automatic-Module-Name of the MANIFEST).
> javadoc:jar fails if project inherits from org.sonatype.oss:oss-parent
> ----------------------------------------------------------------------
>
> Key: MJAVADOC-568
> URL: https://issues.apache.org/jira/browse/MJAVADOC-568
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.1.0
> Environment: maven-javadoc-plugin 3.1.0-SNAPSHOT
> JDK 12-ea+28
> Reporter: Gili
> Priority: Major
> Attachments: testcase.zip
>
>
> # Unpack testcase
> # Run {{mvn clean package javadoc:aggregate -e}}
> # module2 will fail to build with: "javadoc: error - The code being
> documented uses packages in the unnamed module, but the packages defined in
> http://nexus.sonatype.org/oss-repository-hosting.html/root/module1/apidocs/
> are in named modules."
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
