jira-importer commented on issue #967: URL: https://github.com/apache/maven-javadoc-plugin/issues/967#issuecomment-2957365306
**[Gili](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cowwoc)** commented Turns out this had nothing to do with the sonatype parent POM. I fixed the problem by adding: ```java <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <configuration> <archive> <manifestEntries> <Automatic-Module-Name>module2</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </plugin> ``` In other words, if an unnamed module depends upon a named module, then one must set the Automatic-Module-Name entry in the JAR manifest; otherwise, the javadoc tool will fail with the aforementioned error. This is extremely unintuitive. I only got it working because I had an old bug report I filed last year and I saw how I fixed this problem then. Can we please add a check to maven-javadoc-plugin for this situation and output an error message that will point users in the right direction? -- 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]
