[
http://jira.codehaus.org/browse/MJAVADOC-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-100.
------------------------------------
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.3
Added a new goal: javadoc:test-javadoc
For more information, see
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/test-javadocs.apt
> Allow JavaDocs to generate for Test Code
> ----------------------------------------
>
> Key: MJAVADOC-100
> URL: http://jira.codehaus.org/browse/MJAVADOC-100
> Project: Maven 2.x Javadoc Plugin
> Issue Type: New Feature
> Reporter: Jacob Robertson
> Assignee: Vincent Siveton
> Priority: Minor
> Fix For: 2.3
>
>
> I have two use cases.
> First, my team is trying to be very diligent in creating JavaDocs for all our
> code. We have checkstyle checking that javadocs are written for every method
> within test code. So, since we're putting this much effort into our
> javadocs, it's a "nice to have" for those javadocs to actually be generated
> on the project site.
> Second, I have some "Test Harness" code in one project, and this is re-usable
> code which many projects should make use of in their test code. I would like
> to have that code's javadocs available on its project site for obvious
> reasons.
> There is probably some workaround that I could figure out and make this work,
> but much like the Checkstyle plugin has an includeTestSourceDirectory
> property for its goal, adding that type of property to the javadoc plugin
> would be an intuitive way to turn on javadocs for test code.
--
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
