maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antony Stubbs (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-4618) maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules
Date Thu, 02 Jan 2014 15:58:45 GMT

    [ https://jira.codehaus.org/browse/MNG-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338007#comment-338007
] 

Antony Stubbs commented on MNG-4618:
------------------------------------

I also have the same problem with Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
2013-02-19 08:51:28-0500).
                
> maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules
> -------------------------------------------------------------------------
>
>                 Key: MNG-4618
>                 URL: https://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
>             Fix For: 3.0-beta-1
>
>         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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message