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

Philipp Ottlinger commented on RAT-321:
---------------------------------------

a) What kind of format would the configuration have?
* SPDX-recognition string
* license text / header example
or would this feature only be available in the CLI?

As many people use Maven, I'd personally prefer to be able to have this 
available via maven & ant as well.

b) Just out of curiosity: does SPDX support multi-licensing such as
https://github.com/ottlinger/creadur-rat-examples/blob/master/RAT-179/maven/activate-default-licenses-and-add-new-ones/pom.xml

> Allow configuration to define SimplePatternBasedLicense instances
> -----------------------------------------------------------------
>
>                 Key: RAT-321
>                 URL: https://issues.apache.org/jira/browse/RAT-321
>             Project: Apache Rat
>          Issue Type: Improvement
>          Components: engine
>    Affects Versions: 0.15
>            Reporter: Claude Warren
>            Priority: Minor
>
> The concept here is to rework the license matching definitions so that the 
> SimplePatternBasedLicense can be instantiated from a configuration file.
> The reasoning is that there are a number of licences that are of particular 
> interest in projects both inside and outside of the ASF that are not 
> currently included in the code.  This change will allow users to define the 
> string matching for any license that can be matched by simple string matching.
> The proposal is to move all the static definitions into a default file and 
> allow the default to be ignored/overridden.
> *Command Line Flags*
> Add a flag --no-default-file to skip reading the default definitions from 
> within the package.
> Add a flag --definition-file that accepts a file name argument, reads it and 
> adds the definitions to the list of definitions that are checked.  Ensure 
> that multiple --definition-file arguments may provided and that they are 
> added in the order in the --definition-file.
> *Static definition changes*
>  * Modify Meta.Data so that the license family category values are not 
> statically defined.
>  * Modify Meta.Data so that the license family names are not statically 
> defined.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to