[
https://jira.codehaus.org/browse/JXR-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359440#comment-359440
]
Michael Osipov edited comment on JXR-70 at 12/20/14 4:25 PM:
-------------------------------------------------------------
This cannot be solved with JXR unless completely rewritten. JXR is completely
line-based. It would require JXR to create an AST from the source file to be
aware of the current node. This would be a reimplementation of Javadoc in some
way. The difference to MJAVADOC is that is simply passes all parameters to the
Javadoc binary without implementing anything itself.
was (Author: michael-o):
This cannot be solved with JXR unless completely rewritten. JXR is completely
line-based. It would require JXR to create an AST from the source file to be
aware of the current node. This would be a reimplementation of Javadoc in some
way.
> Remove Link to non exisitng javadocs, package access level classes
> ------------------------------------------------------------------
>
> Key: JXR-70
> URL: https://jira.codehaus.org/browse/JXR-70
> Project: Maven JXR
> Issue Type: Improvement
> Components: maven2 jxr plugin
> Affects Versions: 2.1
> Environment: maven2
> Reporter: Vlad Skarzhevskyy
> Labels: close-pending
>
> Link "View Javadoc" created for package access level classes.
> This creates many "404 Not Found" on webserver and hides the real problems on
> website...
> Since maven-javadoc-plugin have it configurable:
> http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#show
> Would be nice to have this as configuration in maven-jxr-plugin.
> linkJavadocShow or linkJavadocAccessLevel
> As well linkJavadocExcludePackageNames may be easy to add for complete
> compatibility with javadoc-plugin excludePackageNames
> Alternative would be to verify if target file exists in directory
> ${javadocDir}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
