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.
Description
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.
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.
Dennis Lundberg added a comment - 10/Feb/09 01:58 AM 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.
New Feature
Open
Major
ejbClient javadoc option
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.