[
https://issues.apache.org/jira/browse/MJAVADOC-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957455#comment-17957455
]
Olivier Lamy commented on MJAVADOC-46:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#541|https://github.com/apache/maven-javadoc-plugin/issues/541].
> Allow -docletpath to be specified as an artifact
> ------------------------------------------------
>
> Key: MJAVADOC-46
> URL: https://issues.apache.org/jira/browse/MJAVADOC-46
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Reporter: Wendy Smoak
> Assignee: Allan Q. Ramirez
> Priority: Minor
> Fix For: 2.0
>
> Attachments: javadoc-docletArtifact.diff
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As suggested (and written!) by Brett Porter on dev@maven, in this thread:
> http://marc.theaimsgroup.com/?l=turbine-maven-dev&m=113694865002748&w=2
> Allow the doclet path to be specified as an artifact with <docletArtifact>.
> Currently the only option is <docletPath> which must be the local path to the
> jar file and is not portable.
> Comments welcome, I'm happy to rework it if necessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
