[
http://jira.codehaus.org/browse/MJAVADOC-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125855
]
Wendy Smoak commented on MJAVADOC-104:
--------------------------------------
Hi Julien. Unfortunately we've had to revert [1] this patch, and it will not
be present in version 2.4 of the plugin.
For more information, please see MJAVADOC-137 and the discussion link in the
previous comment.
If you can solve the problem without the addition of @aggregator, please attach
a new patch.
There is now an integration test to make sure that 'mvn javadoc:jar' continues
to work properly and generate a javadoc jar for each module.
[1] http://svn.apache.org/viewvc?rev=632945&view=rev
> Javadoc of generated sources is not generated when aggregate=true
> -----------------------------------------------------------------
>
> Key: MJAVADOC-104
> URL: http://jira.codehaus.org/browse/MJAVADOC-104
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Julien HENRY
> Assignee: Carlos Sanchez
> Fix For: 2.3
>
> Attachments: javadoc-aggregate.patch
>
>
> Hi,
> If have a multi-module project :
> pom.xml
> |-->moduleA
> |-->moduleB
> I generate source in moduleB.
> 1) If I run mvn javadoc:javadoc in moduleB directory, it works (javadoc of
> the generated class is created)
> 2) If I run mvn javadoc:javadoc from the root directory, with
> aggregate=false, it works (javadoc is in moduleB/target/site/apidocs)
> 3) If I run mvn javadoc:javadoc from the root directory, with aggregate=true,
> it doesn't works (javadoc is in target/site/apidocs but not for the generated
> class)
> Thanks for any help.
--
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
