You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alexander Culum (JIRA)" <ji...@apache.org> on 2016/02/29 01:46:18 UTC

[jira] [Commented] (MPIR-334) Empty Maven Dependency Convergence Report

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

Alexander Culum commented on MPIR-334:
--------------------------------------

Sorry, it must be multi-module, so it won't get much easier.
For me, it stripped out all sub-modules except for one or two - but this is not publicly available. 

> Empty Maven Dependency Convergence Report
> -----------------------------------------
>
>                 Key: MPIR-334
>                 URL: https://issues.apache.org/jira/browse/MPIR-334
>             Project: Maven Project Info Reports Plugin
>          Issue Type: Bug
>          Components: dependency-convergence
>    Affects Versions: 2.8, 2.8.1
>            Reporter: Alexander Culum
>              Labels: close-pending
>
> copied from http://stackoverflow.com/questions/33070728/empty-maven-dependency-convergence-report
> The report section "Dependencies used in modules" is empty if org.apache.maven.plugins:maven-project-info-reports-plugin:2.8.0 or org.apache.maven.plugins:maven-project-info-reports-plugin:2.8.1 is used.
> Solution: use the older version of the plugin org.apache.maven.plugins:maven-project-info-reports-plugin:2.7. A report section 'Dependencies used in sub-projects' is added. This section contains details about the dependency convergence problem in the submodules.



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