You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rupert Smith (JIRA)" <qp...@incubator.apache.org> on 2007/05/29 10:59:15 UTC
[jira] Commented: (QPID-113) no javadoc generation under maven
[ https://issues.apache.org/jira/browse/QPID-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499731 ]
Rupert Smith commented on QPID-113:
-----------------------------------
The javadoc is currently gnerated as part of the site generation. For some reason we cannot execute javadoc:jar against our poms, it complains with:
Not executing Javadoc as the project is not a Java classpath-capable package
I have working examples of javadoc generation for multiprojects, so can copy what works from there.
> no javadoc generation under maven
> ---------------------------------
>
> Key: QPID-113
> URL: https://issues.apache.org/jira/browse/QPID-113
> Project: Qpid
> Issue Type: Task
> Components: Maven build system
> Reporter: Stephen Vinoski
> Fix For: M2
>
>
> We need to generate javadoc in the maven build under the distribution directory. IMO we should either javadoc only the client jar or we should build a new API jar and javadoc that, rather than just javadoc'ing everything.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.