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

2024-04-18 Thread Claude Warren (Jira)


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

Claude Warren commented on RAT-110:
---

[~pottlinger] I believe that this may be fixed in 0.16.1 where you can create a 
configuration file that specifies what license families to accept or reject.

run the command line version and pass the --help for a list of command line 
options.  I believe that the license inclusion/exclusion is implemented in the 
Maven plugin as well.

[~kwin] I believe your suggestion is also implemented in 0.16.1 where you can 
specify no default licenses.

> 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
>Assignee: Claude Warren
>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==
> 
>   
>GNU General Public License, version 
> 3
>.
> 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.20.10#820010)


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

2020-02-10 Thread Konrad Windszus (Jira)


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

Konrad Windszus commented on RAT-110:
-

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==
> 
>   
>GNU General Public License, version 
> 3
>.
> 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)