[
http://jira.codehaus.org/browse/MEJB-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=164706#action_164706
]
Dennis Lundberg commented on MEJB-29:
-------------------------------------
Are you proposing that it should be possible to create a separate jar file
containing the javadocs for the EJB client? I so then I think that would need
to go into the Javadoc Plugin.
If the main artifact is my-ejb-artifact-1.0.jar, then the new javadoc jar would
be my-ejb-artifact-1.0-client-javadoc.jar.
> ejbClient javadoc option
> ------------------------
>
> Key: MEJB-29
> URL: http://jira.codehaus.org/browse/MEJB-29
> Project: Maven 2.x Ejb Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: darren hartford
>
> usecase: Create a client jar that already includes javadoc.
> Either modify the <clientIncludes> to grab files from other locations, or
> modify plugin to integrate to support for Javadoc plugin.
> Note that including the javadoc output to /target/classes includes parts of
> those files within the regular artifact, which is not the intent.
> <clientIncludes>../apidocs/**.*</clientIncludes> does not work.
> <clientInclude>${project.build.directory}/apidocs/**/*.*</clientInclude> does
> not work.
--
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
