[
https://issues.apache.org/jira/browse/MJAVADOC-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763200#comment-17763200
]
Henning Schmiedehausen commented on MJAVADOC-701:
-------------------------------------------------
This is caused by maven looking at the unbuilt project and deciding that it is
a pre-java 9 project (no module-info, no artifact) and thus builds a "legacy"
maven site. When the project is built, it inspects the jar, sees the
automatic-module-name entry and decides that this is a java 9+ project and
builds a module enabled maven site.
This is fixed by MJAVADOC-770 and turning on "legacy" mode.
> javadoc site is broken for projects that contain modules
> --------------------------------------------------------
>
> Key: MJAVADOC-701
> URL: https://issues.apache.org/jira/browse/MJAVADOC-701
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.3.1
> Environment: Maven home: /usr/local/Cellar/maven/3.8.4/libexec
> Java version: 17.0.1, vendor: Eclipse Adoptium, runtime:
> /Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "11.5", arch: "x86_64", family: "mac"
> Reporter: Henning Schmiedehausen
> Priority: Major
>
> How to reproduce:
>
> {{% git clone [https://github.com/hgschmie/pg-embedded.git]}}
> {{% cd pg-embedded}}
> {{% git checkout -b 4.0-branch pg-embedded-4.0}}
> {{% ./mvnw clean site}}
> {{% ls target/site/apidocs}}
> {{allclasses-index.html jquery-ui.overrides.css script-dir}}
> {{allpackages-index.html legal script.js}}
> {{constant-values.html member-search-index.js search.js}}
> {{de module-search-index.js src-html}}
> {{deprecated-list.html overview-summary.html stylesheet.css}}
> {{element-list overview-tree.html tag-search-index.js}}
> {{index-all.html package-search-index.js type-search-index.js}}
> {{index.html resources}}
> {{% ./mvnw clean install site}}
> {{% ls target/site/apidocs}}
> {{allclasses-index.html overview-tree.html}}
> {{allpackages-index.html package-search-index.js}}
> {{constant-values.html resources}}
> {{{color:#ff0000}*de.softwareforge.testing.postgres*{color} script-dir}}
> {{deprecated-list.html script.js}}
> {{element-list search.js}}
> {{index-all.html src}}
> {{index.html src-html}}
> {{jquery-ui.overrides.css stylesheet.css}}
> {{legal tag-search-index.js}}
> {{member-search-index.js type-search-index.js}}
> {{module-search-index.js}}
> ==> If the build only creates the site (run aggregate-no-fork, javadoc,
> javadoc-no-fork), it will not contain the module subfolder
> (de.softwareforge.testing.postgres)
> ==> if the build also runs the "javadoc:jar" goal, the site will contain the
> module subfolder
>
> I have looked through the debug output and the options to the maven javadoc
> plugin execution but nothing stands out. Just that one builds the module
> javadoc correctly and the other does not.
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
