[
https://issues.apache.org/jira/browse/MJAVADOC-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958081#comment-17958081
]
Olivier Lamy commented on MJAVADOC-697:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#1072|https://github.com/apache/maven-javadoc-plugin/issues/1072].
Please visit the GitHub issue to view further activity, add comments, or
subscribe to receive notifications.
> Allowing to register alternative Javadoc implementation
> -------------------------------------------------------
>
> Key: MJAVADOC-697
> URL: https://issues.apache.org/jira/browse/MJAVADOC-697
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: jar
> Affects Versions: 3.1.1
> Reporter: Toni Epple
> Priority: Major
>
> The Maven compiler plugin allows [different implementations of
> compilers|https://maven.apache.org/plugins/maven-compiler-plugin/non-javac-compilers.html]
> to plug in. One of the very useful ones is the [retrofit compiler for
> Java|http://frgaal.org/] that allows one to use syntax of JDK-16 while
> running on old JDKs.
> The compiler works fine, however the problem comes when one wants to generate
> Javadoc. Because the source code is using newer language constructs,
> classical {{javadoc}} from old JDKs fails. One either has to generate the
> Javadoc on a newest JDK (which beats the purpose of retrofit compiler) or
> give up on Javadoc. Or...
> Let's enhance the Maven Javadoc Plugin to support alternative implementations
> of Javadoc, just like the Maven Compiler Plugin does with compilers!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
