Maven 2.x Javadoc Plugin

Creation of Javadoc attachments fails in multi-module project where modules have never been installed/deployed

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.6.1
  • Fix Version/s: 2.8
  • Component/s: None
  • Labels:
    None
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

Running the commands

mvn clean
mvn verify

will fail on the attached demo project with

[INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc'
  has not be previously called for the project: 'org.apache.maven.its.javadoc:mod-b:jar:0.1'.
  Trying to invoke it...
[ERROR] MavenInvocationException: Error when invoking Maven, consult the invoker log file:
  M:\MJAVADOC\mod-a\target\invoker\maven-javadoc-plugin625147587.txt
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] MavenReportException: Error while creating archive:
  Error when invoking Maven, consult the invoker log file: 
  M:\MJAVADOC\mod-a\target\invoker\maven-javadoc-plugin625147587.txt

The command mvn clean verify as usually used during releases will also fail, but starts working after repeated invocations.

Issue Links

This issue is related to:
MJAVADOC-284 detectOfflineLinks sets off extra spurious executions of javadoc Major Closed
This issue is depended upon by:
MJAVADOC-276 Initial builds of a multi-module project fail Blocker Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Benjamin Bentmann added a comment -

I guess that the same issue already reported as Regression with maven-javadoc-plugin 2.6.1 and release:perform.

Show
Benjamin Bentmann added a comment - I guess that the same issue already reported as Regression with maven-javadoc-plugin 2.6.1 and release:perform.
Hide
Permalink
Julien HENRY added a comment -

I agree I think this is the same issue.

Show
Julien HENRY added a comment - I agree I think this is the same issue.
Hide
Permalink
Benjamin Bentmann added a comment -

This is in particular problematic as not even "mvn install" makes it work.

Show
Benjamin Bentmann added a comment - This is in particular problematic as not even "mvn install" makes it work.
Hide
Permalink
Hans Beemsterboer added a comment -

I had a similar issue, while running: mvn site.
After explicitly running: mvn javadoc:javadoc, this issue didn't occur any more.

Show
Hans Beemsterboer added a comment - I had a similar issue, while running: mvn site. After explicitly running: mvn javadoc:javadoc, this issue didn't occur any more.
Hide
Permalink
Harold Shinsato added a comment -

This is happening for us only during release:perform - is there any workaround? It's confusing why the javadoc for one project gets invoked from another project.

Show
Harold Shinsato added a comment - This is happening for us only during release:perform - is there any workaround? It's confusing why the javadoc for one project gets invoked from another project.
Hide
Permalink
Frederick N. Brier added a comment -

I believe I was having this issue with version 2.6.1/Maven 2.2.1. If I comment out the plugin, it builds fine. Otherwise, the preceding sibling dependency is "missing". I just checked out/built/installed the 2.7-SNAPSHOT and the error is still occurring.

Show
Frederick N. Brier added a comment - I believe I was having this issue with version 2.6.1/Maven 2.2.1. If I comment out the plugin, it builds fine. Otherwise, the preceding sibling dependency is "missing". I just checked out/built/installed the 2.7-SNAPSHOT and the error is still occurring.
Hide
Permalink
Dinesh Mehta added a comment -

I still see this error with v2.7. What are the configurations to run the plugin in aggreagte mode for a multi-module project?

Show
Dinesh Mehta added a comment - I still see this error with v2.7. What are the configurations to run the plugin in aggreagte mode for a multi-module project?
Hide
Permalink
Yegor Bugayenko added a comment -

The problem is still not fixed. Why the issue is closed?

Show
Yegor Bugayenko added a comment - The problem is still not fixed. Why the issue is closed?
Hide
Permalink
Dan Tran added a comment -

reopen since javadoc plugin 2.7 still see the same issue

Show
Dan Tran added a comment - reopen since javadoc plugin 2.7 still see the same issue
Hide
Permalink
John Casey added a comment -

what about 2.8? can we close this issue now that MJAVADOC-284 is closed? I haven't seen it, unless you're talking about the case where the javadoc plugin forks a new build in order to produce javadocs for dependencies...for which there is a flag to skip that, and I'm assuming MJAVADOC-284 has fixed in a more permanent way.

Show
John Casey added a comment - what about 2.8? can we close this issue now that MJAVADOC-284 is closed? I haven't seen it, unless you're talking about the case where the javadoc plugin forks a new build in order to produce javadocs for dependencies...for which there is a flag to skip that, and I'm assuming MJAVADOC-284 has fixed in a more permanent way.
Hide
Permalink
Herve Boutemy added a comment -

yes, with MJAVADOC-284 fixed, this issue is a duplicate IMHO

Show
Herve Boutemy added a comment - yes, with MJAVADOC-284 fixed, this issue is a duplicate IMHO

People

Vote (12)
Watch (19)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.