[
https://issues.apache.org/jira/browse/MJAVADOC-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958106#comment-17958106
]
Olivier Lamy commented on MJAVADOC-717:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#1106|https://github.com/apache/maven-javadoc-plugin/issues/1106].
Please visit the GitHub issue to view further activity, add comments, or
subscribe to receive notifications.
> Support Maven-Site approach
> ---------------------------
>
> Key: MJAVADOC-717
> URL: https://issues.apache.org/jira/browse/MJAVADOC-717
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Reporter: Stephen Crocker
> Priority: Major
>
> The maven-javadoc-plugin currently creates its own independent website using
> Jquery, etc.. This means javadoc always looks separate from a site produced
> file.
> I would like to rewrite the plug-in so it uses the same Apache Velocity based
> template approach as the maven-site-plugin (and can be pointed at a
> maven-site-directory), the javadoc design should then sit within the same
> format as that generated output.
> I've noticed there is the 'java' and 'maven' style, I purpose the new
> approach is only taken for 'maven' projects with the existing code used for
> the 'java' type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
