[ 
https://issues.apache.org/jira/browse/MEJB-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17966055#comment-17966055
 ] 

Olivier Lamy commented on MEJB-29:
----------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-ejb-plugin#82|https://github.com/apache/maven-ejb-plugin/issues/82].
 

> ejbClient javadoc option
> ------------------------
>
>                 Key: MEJB-29
>                 URL: https://issues.apache.org/jira/browse/MEJB-29
>             Project: Maven EJB Plugin (Moved to GitHub Issues)
>          Issue Type: New Feature
>    Affects Versions: 2.1
>            Reporter: Darren Hartford
>            Assignee: Karl Heinz Marbaise
>            Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to