[jira] [Created] (MPIR-397) dependency-management report fails on managed dependencies with 'null' version

["Carsten Rohde (Jira)" <ji...@apache.org>]

Carsten Rohde created MPIR-397:
----------------------------------

             Summary: dependency-management report fails on managed dependencies with 'null' version
                 Key: MPIR-397
                 URL: https://issues.apache.org/jira/browse/MPIR-397
             Project: Maven Project Info Reports Plugin
          Issue Type: Bug
          Components: dependency-management
    Affects Versions: 3.1.0, 3.0.0, 2.9, 2.7
         Environment: Microsoft Windows 10, Maven 3.5.4, Azul OpenJDK8 or Azul OpenJDK7
            Reporter: Carsten Rohde
         Attachments: pirbug-aggregator.zip

Maven allows to have managed dependencies without a version. This can be very useful, because this way you can change the scope of a transitive dependency without affecting the resolved version.

The dependency-management report however fails under such circumstances:
{code:java}
Error generating maven-project-info-reports-plugin:3.1.0:dependency-management report: For artifact {pirbugdemo:pirbug-transitive:null:jar}: The version cannot be empty
{code}
There has been a similar issue with the versions-maven-plugin: https://github.com/mojohaus/versions-maven-plugin/issues/114

 

The example mainly consists of a "consumer" module with a dependency to a "dependency" module wich in turn has a dependency to a third module "transitive". In the consumer module, the "transitive" dependency is managed without setting the version.

If there is a workaround, please let me know.

 

Thanks a lot!

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)