[jira] [Comment Edited] (RAT-110) Add a maven configuration option to define a target license in order to mark a project as compliant

["Konrad Windszus (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/RAT-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033906#comment-17033906 ] 

Konrad Windszus edited comment on RAT-110 at 2/10/20 7:55 PM:
--------------------------------------------------------------

I think by default the pom element {{licenses}} (http://maven.apache.org/pom.html#Licenses) should be evaluated and only license headers belonging to those licenses should be approved.


was (Author: kwin):
I think by default the pom element {{licenses}} should be evaluated and only license headers belonging to those licenses should be approved.

> Add a maven configuration option to define a target license in order to mark a project as compliant
> ---------------------------------------------------------------------------------------------------
>
>                 Key: RAT-110
>                 URL: https://issues.apache.org/jira/browse/RAT-110
>             Project: Apache Rat
>          Issue Type: Improvement
>    Affects Versions: 0.9
>            Reporter: Philipp Ottlinger
>            Priority: Major
>
> Currently rat searches for ASLed files. In order to broaden the usage of this tool I'd like to add a new maven configuration option that allows the definition of a target license.
> This license has to exist in RAT and changes the output of the rat report but does not change the default behaviour for backwards compatibility.
> =OLD REPORT=
> *****************************************************
> Summary
> -------
> Notes: 1
> Binaries: 187
> Archives: 0
> Standards: 149
> Apache Licensed: 2
> ....
> *****************************************************
>   Files with Apache License headers will be marked AL
> .....
> =NEW REPORT=
> If no configuration option is supplied above report stays the same, but may change for different licenses (e.g. GPL / RAT-13).
> ==MVN CONFIGURATION==
>     <configuration>
>            <!-- define family value name of target license -->   
>            <defaultLicenseName>GNU General Public License, version 3</defaultLicenseName>
>            .....
> will lead to the output:
> ==FLEXIBLE REPORT==
> *****************************************************
> Summary
> -------
> Notes: 1
> Binaries: 187
> Archives: 0
> Standards: 149
> GPL3 Licensed: 2
> ....
> *****************************************************
>   Files with GNU General Public License, version 3 headers will be marked GPL3.
> ...
> Since I do have a patch for RAT-13 this were the next step to realise a multilicense usage of rat.



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