[ 
https://issues.apache.org/jira/browse/MJAVADOC-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17065421#comment-17065421
 ] 

Michael Osipov commented on MJAVADOC-645:
-----------------------------------------

We should fix the root cause, not the symptom: {{javadoc(1)}. Please report 
this on the Javadoc mailing list first.

> Remind user to add Automatic-Module-Name entry when an unnamed module depends 
> on a named module
> -----------------------------------------------------------------------------------------------
>
>                 Key: MJAVADOC-645
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-645
>             Project: Maven Javadoc Plugin
>          Issue Type: Improvement
>          Components: jar, javadoc
>    Affects Versions: 3.2.0
>            Reporter: Gili
>            Priority: Major
>         Attachments: testcase.zip
>
>
> 1. Extract testcase
> 2. Run `mvn clean package`
> 3. Build fails with:
> {code:java}
> Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.2.0:jar (attach-javadocs) on 
> project module2: MavenReportException: Error while generating Javadoc: 
> Exit code: 1 - 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.
> Command line was: cmd.exe /X /C ""C:\Program 
> Files\Java\jdk-14+36-1461\bin\javadoc.exe" @options @packages"
> Refer to the generated Javadoc files in 
> 'C:\Users\Gili\Documents\3rdparty\javadoc-jar-mixing-named-and-unnamed-extending-sonatype\module2\target\apidocs'
>  dir.
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to