[jira] [Comment Edited] (MJAVADOC-437) javadoc:aggregate fails on initial build

["Michael Osipov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MJAVADOC-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042298#comment-15042298 ] 

Michael Osipov edited comment on MJAVADOC-437 at 12/4/15 9:58 PM:
------------------------------------------------------------------

I would take MJAVADOC-275 IT as a starting point. Adapt names and classes and make it fail without your patch first. When it fails consistently, apply your patch and see what happens. The Invoker Plugin will create a new local repo after each clean phase, you should be able to reproduce your issue. If you have trouble, just ping me.


was (Author: michael-o):
I would take MJAVADOC-275 as a starting point. Adapt names and classes and mail it fail without your patch first. When it fails consistently, apply your patch and see what happens. The Invoker Plugin will create a new local repo after a clean, you should be able to reproduce your issue. If you have trouble, just ping me.

> 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
>
> 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)