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

["Nicholas Williams (JIRA)" <ji...@codehaus.org>]

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

Nicholas Williams commented on MNG-4618:
----------------------------------------

I don't know whether this can be re-opened or whether I should clone it or what. This bug was either not fixed, or it has become re-broken.

I'm using Maven 3.0.3:

Apache Maven 3.0.3 (r1075438; 2011-02-28 11:31:09-0600)
Maven home: /usr/share/maven
Java version: 1.7.0_07, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac"

Here is my plugin configuration:

{code:xml}<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-javadoc-plugin</artifactId>
    <version>2.9</version>
    <configuration>
        <outputDirectory>out/apidocs</outputDirectory>
        <reportOutputDirectory>out/artifacts/apidocs</reportOutputDirectory>
        <jarOutputDirectory>out/artifacts</jarOutputDirectory>
        <finalName>${project.groupId}-${project.artifactId}-${project.version}</finalName>
        <maxmemory>${project.tasks.maximum.memory}</maxmemory>
        <show>protected</show>
        <version>true</version>
        <use>true</use>
        <author>true</author>
        <windowtitle>${project.name} ${project.version}</windowtitle>
        <breakiterator>true</breakiterator>
        <failOnError>true</failOnError>
        <doctitle><![CDATA[<h2>${project.name} ${project.version} API Documentation</h2>]]></doctitle>
        <bottom>
            <![CDATA[<i>Copyright &#169; 2010-2013 Nicholas Williams. All Rights Reserved. Licensed
                Under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License version
                2.0</a>.</i>]]>
        </bottom>
        <detectJavaApiLink>true</detectJavaApiLink>
        <detectLinks>true</detectLinks>
        <links>
            <link>http://commons.apache.org/cli/api-1.2/</link>
            <link>http://commons.apache.org/codec/api-1.7/</link>
            <link>http://commons.apache.org/io/api-2.4/</link>
        </links>
        <sourceFileExcludes>
            <exclude>net/nicholaswilliams/java/mock/**</exclude>
            <exclude>net/nicholaswilliams/java/licensing/mock/**</exclude>
            <exclude>net/nicholaswilliams/java/licensing/samples/**</exclude>
            <exclude>**Mock*.java</exclude>
        </sourceFileExcludes>
    </configuration>
    <executions>
        <execution>
            <id>make-javadoc</id>
            <phase>package</phase>
            <goals>
                <goal>aggregate-jar</goal>
            </goals>
            <inherited>false</inherited>
        </execution>
    </executions>
</plugin>{code}

When run with `mvn package`, I get the exact same [WARNING] he describes above (except with my artifacts). I can ONLY successfully aggregate JavaDocs by removing the <executions> and calling `mvn package javadoc:aggregate-jar` instead.
                
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira