[
http://jira.codehaus.org/browse/MJAVADOC-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125995
]
wsmoak edited comment on MJAVADOC-119 at 3/3/08 8:32 PM:
--------------------------------------------------------------
I originally thought this may have been fixed along with MJAVADOC-137 by
reverting the change from MJAVADOC-104 that added @aggregator, but now I see
that it was reported against v2.2.
was (Author: wsmoak):
I believe this was fixed along with MJAVADOC-137 by reverting the change
from MJAVADOC-104 that added @aggregator.
> Aggregate does not work for multiple module project when doing install.
> -----------------------------------------------------------------------
>
> Key: MJAVADOC-119
> URL: http://jira.codehaus.org/browse/MJAVADOC-119
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: Fedora Linux, Maven 2.0.6
> Reporter: Paul Gier
> Fix For: 2.4
>
>
> If have a multi-module project, the javadoc aggregate does not find
> inter-module dependencies:
> pom.xml
> |-->module1
> |-->module2
> module 1 depends on module 2
> The javadoc plugin is added to the build lifecycle attached to the install
> phase. When I run "mvn install" I get a "Failed to resolve artifact." error
> message looking for module 2.
--
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