Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.3.1
-
None
Description
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
de.softwareforge.testing.postgres 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.
Attachments
Issue Links
- is fixed by
-
MJAVADOC-770 Allow building javadoc "the old fashioned way" after Java 8
- Closed