You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Shannon Carey (JIRA)" <ji...@apache.org> on 2016/10/06 18:30:20 UTC

[jira] [Commented] (MJAVADOC-467) Aggregator reports should not require modules to be installed/deployed.

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

Shannon Carey commented on MJAVADOC-467:
----------------------------------------

Wouldn't this give inaccurate report information in a multimodule build if, for example, you ran:

```
git checkout v1
mvn compile
git checkout v2
mvn clean deploy site-deploy
```

When the second maven command is run, the reactor module will be cleaned, deployed, and then the javadoc:aggregate will be run. However, the child modules have not executed any phases and therefore the aggregate report will gather data based on the "v1" branch previously compiled.

Or does this change fix that issue somehow?

> Aggregator reports should not require modules to be installed/deployed.
> -----------------------------------------------------------------------
>
>                 Key: MJAVADOC-467
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-467
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>            Reporter: Christian Schulte
>            Assignee: Christian Schulte
>            Priority: Trivial
>             Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)