regression: Adding "jar" execution to the parent of a multi-module javadoc plugin causes "recursive invocations" error

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.3
  • Fix Version/s: 2.4
  • Labels:
    None

Description

I have a multimodule project with the javadoc plugin declared in my parent.

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.3</version>
<configuration>
<aggregate>true</aggregate>
</configuration>
<executions>
<execution>
<id>attach-javadocs</id>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>

After upgrading to 2.3 and do a build I now get the error:

[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping

Which then skips the processing of that module and later gives me dependency errors because previous dependencies were not compiled.

If I remove jar processing from my plugin definition everything works fine except no javadoc jars are created.

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. MJAVADOC-137 javadoc:javadoc always runs as "aggregator"

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Siveton added a comment -

Is it defined in <build/> or <reporting/> section

Show
Vincent Siveton added a comment - Is it defined in <build/> or <reporting/> section
Hide
Permalink
Mike Youngstrom added a comment -

I have the above in the <build/> section and I have below in the <reporting/> section since I don't believe it's possible to add executions to plugings in the <reporting/> section???

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.3</version>
<configuration>
<aggregate>true</aggregate>
</configuration>
</plugin>

Show
Mike Youngstrom added a comment - I have the above in the <build/> section and I have below in the <reporting/> section since I don't believe it's possible to add executions to plugings in the <reporting/> section??? <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-javadoc-plugin</artifactId> <version>2.3</version> <configuration> <aggregate>true</aggregate> </configuration> </plugin>
Hide
Permalink
Nick Belaevski added a comment - - edited

We seem to have the similar problem. Build fails because of missing dependencies to reactor projects with "jar" packaging. Switching to 2.2 version solves the problem.

Here is the link to our source repository: http://anonsvn.jboss.org/repos/richfaces/trunk/ (use revision 2120); framework project contains Javadoc plugin invocation for nested api, impl, test projects. ui/core project depends on framework but fails to build because of missing .jar files in local repository (I've ran Maven in offline mode). Please inform me if you need more info to investigate the problem: build logs, comments on Richfaces project structure and inner dependencies etc.

Show
Nick Belaevski added a comment - - edited We seem to have the similar problem. Build fails because of missing dependencies to reactor projects with "jar" packaging. Switching to 2.2 version solves the problem. Here is the link to our source repository: http://anonsvn.jboss.org/repos/richfaces/trunk/ (use revision 2120); framework project contains Javadoc plugin invocation for nested api, impl, test projects. ui/core project depends on framework but fails to build because of missing .jar files in local repository (I've ran Maven in offline mode). Please inform me if you need more info to investigate the problem: build logs, comments on Richfaces project structure and inner dependencies etc.
Hide
Permalink
Vincent Siveton added a comment -

Thanks Nick! The causes seems to be @aggregator in AbstractJavadocMojo.

Show
Vincent Siveton added a comment - Thanks Nick! The causes seems to be @aggregator in AbstractJavadocMojo.
Hide
Permalink
Jörg Hohwiller added a comment -

FYI: This issue broke my build, too. It took me a long time to figure out what whas going wrong. Since the logfiles dont give a clue about the problem (at least to a regular human). It would help to create, test and release an update to the javadoc plugin.

Show
Jörg Hohwiller added a comment - FYI: This issue broke my build, too. It took me a long time to figure out what whas going wrong. Since the logfiles dont give a clue about the problem (at least to a regular human). It would help to create, test and release an update to the javadoc plugin.
Hide
Permalink
Wendy Smoak added a comment -

I believe this was fixed along with MJAVADOC-137 by reverting the change from MJAVADOC-104 that added @aggregator.

Show
Wendy Smoak added a comment - I believe this was fixed along with MJAVADOC-137 by reverting the change from MJAVADOC-104 that added @aggregator.
Hide
Permalink
Wendy Smoak added a comment -

Closing based on Vincent's comment that the cause was @aggregator, which has since been removed.

Show
Wendy Smoak added a comment - Closing based on Vincent's comment that the cause was @aggregator, which has since been removed.

People

  • Assignee:
    Wendy Smoak
    Reporter:
    Mike Youngstrom
Vote (9)
Watch (8)

Dates

  • Created:
    Updated:
    Resolved: