maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qadeer Ahmad (JIRA)" <>
Subject [jira] (MNG-4618) maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules
Date Fri, 03 Jan 2014 18:20:45 GMT


Qadeer Ahmad commented on MNG-4618:

I have the same problem. See my stackoverflow [question|].
> maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules
> -------------------------------------------------------------------------
>                 Key: MNG-4618
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.0-alpha-7
>            Reporter: bob mcwhirter
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0-beta-1
>         Attachments:
> 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, please contact your JIRA administrators
For more information on JIRA, see:

View raw message