[
https://issues.apache.org/jira/browse/MJAVADOC-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753157#comment-16753157
]
Gili commented on MJAVADOC-568:
-------------------------------
That's a good catch for the MANIFEST.MF file. Can you please improve the error
message if the user fails to provide the manifest attribute (by accident or
intentionally)? In such a case I still get the original error message which
does not hint that adding a manifest would make a difference.
I also just found another bug which I will be filing momentarily.
> javadoc:jar fails when project has Automatic-Module-Name and (implicit) uses
> offlinelinks with element-list
> -----------------------------------------------------------------------------------------------------------
>
> 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
> Assignee: Robert Scholte
> 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)
