You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2019/12/15 21:04:00 UTC
[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.
[ https://issues.apache.org/jira/browse/MPIR-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylwester Lachiewicz updated MPIR-351:
--------------------------------------
Labels: (was: beginner patch)
> 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
>
> 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
(v8.3.4#803005)