maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harald Wellmann (JIRA)" <>
Subject [jira] [Commented] (MJAVADOC-437) javadoc:aggregate fails on initial build
Date Sun, 06 Dec 2015 21:48:11 GMT


Harald Wellmann commented on MJAVADOC-437:

The point is, the test needs at least one external dependency for the bug to show. 

javadoc will see all the _sources_ of the current reactor, even when the dependencies can't
be resolved. But if a module has an internal and an external dependency, failure of resolving
the internal one will lead to _all_ dependencies being skipped. The choice of {{commons-io}}
as external dependency is completely arbitrary. 

I've cleaned up all the unnecessary dependencies and other stuff I overlooked. Thanks for
the review!

> javadoc:aggregate fails on initial build
> ----------------------------------------
>                 Key: MJAVADOC-437
>                 URL:
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.10.3
>            Reporter: Harald Wellmann
>            Assignee: Michael Osipov
> h3. Scenario
> Take a SNAPSHOT version of a reactor project with at least two JAR modules.
> Assume that no artifacts of the given SNAPSHOT version have been built before (this is
usually the case just after running release:perform).
> h3. Actual Behaviour
> Now run {{mvn javadoc:aggregate}}. This build fails in the forked lifecycle. maven-javadoc-plugin
unnecessarily tries to resolve the JAR artifacts of the current reactor (which are not avialable
yet) and add them to the Javadoc classpath.
> h3. Expected Behaviour
> Aggregated Javadoc should be generated without problems. It is sufficient to take the
sources of the current reactor and only put *external* dependencies on the Javadoc classpath.
> This is a duplicate of an 8 year old bug MJAVADOC-116 with 51 votes which has been closed
without being fixed.
> A patch for this problem was submitted in MJAVADOC-362, but does not seem to have received
attention by committers. (I admit the problem description is not very clear.)

This message was sent by Atlassian JIRA

View raw message