[jira] Reopened: (MNG-4618) maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules

["bob mcwhirter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

bob mcwhirter reopened MNG-4618:
--------------------------------


If you like, you can try on the TorqueBox project:

http://github.com/torquebox/torquebox/tree/module-refactor

Git clone from

git@github.com:torquebox/torquebox.git

And try the module-refactor branch.

At the moment, it should work, due to my huge <dependencies> section in the top-level pom.

http://github.com/torquebox/torquebox/blob/module-refactor/pom.xml

> maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules
> -------------------------------------------------------------------------
>
>                 Key: MNG-4618
>                 URL: http://jira.codehaus.org/browse/MNG-4618
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.0-alpha-7
>            Reporter: bob mcwhirter
>            Assignee: Benjamin Bentmann
>         Attachments: MNG-4618.zip
>
>
> Binding javadoc:aggregate-jar to package in an aggregator project works with maven 2.
> In maven3, it attempts to build the aggregate javadocs before completing the full reactor.
> When executing 'mvn install', I'd expect it to run the reactor and install all modules before attempting the 'compile' dependency resolution for the javadoc execution.
> During early execution, I get output such as:
> {noformat}
> [WARNING] The dependency: [org.torquebox:torquebox-common-spi:jar:1.0.0.Beta19] can't be resolved but has been found in the reactor (probably snapshots).
> This dependency has been excluded from the Javadoc classpath. You should rerun javadoc after executing mvn install.
> {noformat}
> In maven2, it'd react, install all submodules, then, as the last act, do the javadoc:aggregate-jar.
> If I add a <dependency> for each module to the maven-javadoc-plugin's <dependencies> section, then it will get the order correct.  I'd just kinda think that'd be implicit.

-- 
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