[
http://jira.codehaus.org/browse/MJAVADOC-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136381#action_136381
]
Matthew Beermann commented on MJAVADOC-97:
------------------------------------------
I specifically avoided that approach, since it assumes a) that the project is
using WebDAV to deploy the site, and b) that the publishing URL is the same as
the public access URL. Those both seem like very large assumptions; larger, in
my view, than the assumption about the <url> field...
> enable internal/external dependency references as links
> --------------------------------------------------------
>
> Key: MJAVADOC-97
> URL: http://jira.codehaus.org/browse/MJAVADOC-97
> Project: Maven 2.x Javadoc Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Richard van Nieuwenhoven
> Assignee: Kenney Westerhof
> Priority: Minor
> Attachments: maven-javadoc-plugin-2.1.patch,
> MJAVADOC-97-maven-javadoc-plugin.patch
>
>
> This patch enables the java doc plugin to autmaticaly connect the dependent
> javadoc pages as links.
> There is no more need to add links in your pom's for internal and external
> maven projects.
> The plugin resolves the dependencies and adds the defined project url's
> extended with "/apidocs" to the links in the plugin.
> TODO: a warning occures when the project has no javadocs (or no maven
> generated javadoc on its homepage) ......
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
