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

Claude Warren commented on RAT-321:
-----------------------------------

The initial code for this idea is complete. 

 

What is needed is:

DOCUMENTATION – there is a radical change to how additional licenses are 
defined in the cli, ANT, and Maven interfaces.  This needs to be documented 
somewhere on the RAT site, but I don't see any documentation currently 
available.  If someone can point to where this might be it would be helpful.

Removal of old constants.  Many of the old values still exist in the MetaData 
directory.  These should be marked as deprecated and removed later.

Documentation for how to convert older Ant and Maven definitions to new form.

 

> 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