Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: javadoc-plugin
-
Environment:Jenkins Version : Jenkins ver. 1.642.1
OS : Red Hat Enterprise Linux 6.5
Javadoc built from a freestyle project using maven javadoc:javadoc top-level target.
-
Similar Issues:
-
Released As:Javadoc Plugin 1.5
Description
When building a project in freestyle mode using Apache Maven 3.3.9 and creating the javadoc using the javadoc:javadoc top-level target, the Javadoc link appears on the project's dashboard, but when clicking it, only a blank Documentation frame appears without the content of the Javadoc.
I should point out that the data IS there, since I opened the index.html file in my browser and it displayed perfectly.
Attached is the result from clicking the Javadoc button and the Javadoc itself when launched via the index.html.
Any help would be appreciated.
Attachments
Issue Links
- is related to
-
-
- Resolved
-
- links to
Activity
The **/package-summary.html can not be used as an index page either as it does not reside in the project root (obviously, it is summary of a java package) and therefore it refers to resources as ../../../foo.bar which obviously fails. In theory, this can be overcome by not using it as an index page for DirectoryBrowserSupport but modifying the JavadocAction too redirect to it instead so it is rendered at expected path.
I gave up decided to keep things simple and used overview-tree.html that is not ideal but prone of all those issues: https://github.com/jenkinsci/javadoc-plugin/pull/10
https://github.com/jenkinsci/javadoc-plugin/pull/10 needs to be released to close it
I have released 1.5 today which should integrate the recent reports
Wrong status in that case.
It even seems javadoc 11 redirects from overview-summary.html to index.html for multipackage projects while it redirects from index.html to the only package-summary.html available in case of singlepackage project. IOW, none of the locations is safe to use.