[
http://jira.codehaus.org/browse/MJAVADOC-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137908#action_137908
]
Andrea Aime commented on MJAVADOC-78:
-------------------------------------
I don't have exactly a test case, but I can attach the pom that we had to make
to make things work, as you can see there is a profile that activates the usage
of the special doclet and reconfigures the javadoc plugin accordinly (see the
javadoc config in build and then the "uml" profile near the end).
> Add a flag to provide standard doclet parameters to custom ones too
> -------------------------------------------------------------------
>
> Key: MJAVADOC-78
> URL: http://jira.codehaus.org/browse/MJAVADOC-78
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: Andrea Aime
> Attachments: JAVADOC-78.patch, pom.xml
>
>
> I'm working on a custom doclet that wraps the standard doclet and add extra
> behaviour (automated class diagram generation in class javadocs and package
> javadocs). I want to run it under maven 2, but I've stumbled against the
> default behaviour: standard doclet parameters such as -link are provided only
> if the javadoc is the standard one (in AbstractJavadocMojo.java, the check is
> "if ( StringUtils.isEmpty( doclet ) ) ...").
> A generally good behaviour would be not perform assumptions, but to call
> XXXDoclet.optionLength for each parameter, and see if the doclet accepts them
> or not (and thus provide only the one accepted). As an alternative, add at
> least a flag to allow the provision of the standard doclet parameters to the
> custom ones as well.
--
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
