jira-importer commented on issue #858: URL: https://github.com/apache/maven-javadoc-plugin/issues/858#issuecomment-2957357908
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented 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). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
