[
https://issues.apache.org/jira/browse/MJAVADOC-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862221#comment-16862221
]
Jessica-Aileen Alten commented on MJAVADOC-608:
-----------------------------------------------
Same problem here - and there seems to be no chance to skip over this pom type
module (perhaps another bug?)
> Unable to run javadoc:aggregate on multi-module projects with one or more pom
> modules when using Java modules (jigsaw).
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: MJAVADOC-608
> URL: https://issues.apache.org/jira/browse/MJAVADOC-608
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.1.0
> Reporter: Anders Hanson
> Priority: Major
> Attachments: module-test.zip
>
>
> The following error is displayed and build fail when runnin mvn
> javadoc:aggregate on a multi-module project where one or more child modules
> are of pom type (<packaing>pom</packaging>) when using mavan modules (jigsaw)
>
> [ERROR] Creating an aggregated report for both named and unnamed modules is
> not possible.
> [ERROR] Ensure that every module has a module descriptor or is a jar with a
> MANIFEST.MF containing an Automatic-Module-Name.
> I've attached a minimal project showing the problem. Run either mvn
> javadoc:aggregate or mvn site:site
> maven module with packaging pom should be excluded from the unnames module
> lest, they are not java modules and will not produce any jar files, named or
> not.
> This is with maven 3.6.0 and jdk 11.0.3 (latest AdoptJDK)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
