Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Mon, 7 Dec 2015 18:28:11 +0000 (UTC)
From: "Michael Osipov (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.12918111.1449172761000.291970.1449512891142@Atlassian.JIRA>
In-Reply-To: <JIRA.12918111.1449172761000@Atlassian.JIRA>
References: <JIRA.12918111.1449172761000@Atlassian.JIRA>
 <JIRA.12918111.1449172761167@arcas>
Subject: [jira] [Closed] (MJAVADOC-437) javadoc:aggregate fails on initial
 build
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MJAVADOC-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MJAVADOC-437.
-----------------------------------
    Resolution: Fixed

Fixed with [r1718436|http://svn.apache.org/r1718436].

> javadoc:aggregate fails on initial build
> ----------------------------------------
>
>                 Key: MJAVADOC-437
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-437
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.10.3
>            Reporter: Harald Wellmann
>            Assignee: Michael Osipov
>             Fix For: 2.10.4
>
>
> 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
(v6.3.4#6332)