[jira] [Updated] (MPIR-351) Adding functionality to dependencies goal in order to integrate with maven license plugin and source missing licenses from specified properties file.

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

     [ https://issues.apache.org/jira/browse/MPIR-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated MPIR-351:
--------------------------------
    Fix Version/s: waiting-for-feedback

> Adding functionality to dependencies goal in order to integrate with maven license plugin and source missing licenses from specified properties file.
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MPIR-351
>                 URL: https://issues.apache.org/jira/browse/MPIR-351
>             Project: Maven Project Info Reports Plugin
>          Issue Type: Improvement
>          Components: dependencies
>    Affects Versions: 2.9
>            Reporter: Aneesh Natarajan
>            Priority: Major
>              Labels: beginner, patch
>             Fix For: waiting-for-feedback
>
>
> The maven license plugin produces a THIRD-PARTY.properties file with each of the third party libraries with missing licensing information. The patch that I am proposing uses those properties file to source licensing information when developing the dependencies.html reports. It would include the following:
>       - Add configurable property dependency.license.resource that specifies the path of the properties file 
>       - Have MavenProject object source licensing information from properties file, when license block is not available in pom.xml file of dependency. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)