You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2008/03/06 03:46:28 UTC

[jira] Commented: (MJAVADOC-119) Aggregate does not work for multiple module project when doing install.

    [ http://jira.codehaus.org/browse/MJAVADOC-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126250 ] 

Wendy Smoak commented on MJAVADOC-119:
--------------------------------------

@aggregator has been removed.  If this is still a problem, please provide a sample project and steps to reproduce it.

I'd like to stage the 2.4 release this weekend, and plan to remove this from the 2.4 bucket if no fix or example is provided.

> 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
> |--&gt;module1
> |--&gt;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