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

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.7, 2.9, 3.0.0, 3.1.0
• Component/s: dependency-management
• Environment: Microsoft Windows 10, Maven 3.5.4, Azul OpenJDK8 or Azul OpenJDK7
• External issue URL: https://github.com/mojohaus/versions-maven-plugin/issues/114
• Assignee: Unassigned
• Reporter: Carsten Rohde
• Created: 15/Jul/20 15:25
• Updated: 27/May/23 11:37

Description

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:

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

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!