Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Wed, 16 Nov 2016 22:23:59 +0000 (UTC)
From: "Aneesh Natarajan (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.13021290.1479334987000.297759.1479335039499@Atlassian.JIRA>
In-Reply-To: <JIRA.13021290.1479334987000@Atlassian.JIRA>
References: <JIRA.13021290.1479334987000@Atlassian.JIRA> <JIRA.13021290.1479334987391@arcas>
Subject: [jira] [Created] (MPIR-351) Adding functionality to dependencies
 goal in order to integrate with maven license plugin and source missing
 licenses from specified properties file.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 16 Nov 2016 22:24:01 -0000

Aneesh Natarajan created MPIR-351:
-------------------------------------

             Summary: 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


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
(v6.3.4#6332)