[
https://issues.apache.org/jira/browse/RAT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549871#comment-14549871
]
Maxim Solodovnik commented on RAT-179:
--------------------------------------
Just have checked: 0.12-SNAPSHOT works as expected in our maven build. Thanks!
Will attach ant sample project shortly
> Maven plugin and Ant task do not support adding extra approved licences
> -----------------------------------------------------------------------
>
> Key: RAT-179
> URL: https://issues.apache.org/jira/browse/RAT-179
> Project: Apache Rat
> Issue Type: Bug
> Components: antlib, maven
> Affects Versions: 0.11
> Reporter: Sebb
> Assignee: Philipp Ottlinger
> Attachments: RAT-179.tar.gz
>
>
> Users can add new license types using the <licenses> tag.
> h3. Affects: Maven- and ANT plugin
> h4. Maven
> These are not added to the approved licenses list.
> This has to be done through the <licenseFamilies> tag.
> However, the entries replace the defaults.
> There does not appear to be any way to update the approved list other than
> replacing it entirely, which is very inconvenient.
> This could be fixed by adding a new property analagous to
> addDefaultLicenseMatchers, e.g. addDefaultLicenseFamilies
> Or it might be easier for the user to configure if individual <license>
> entries could be tagged as approved. The default would need to be false for
> backwards compatibility.
> h4. Ant
> Same issue for Ant task; <rat:approvedLicense/> configs replace the default
> set.
> Reported by [~solomax] via
> [mail|http://rat.markmail.org/thread/3qdpynxpejujbzm7#query:+page:1+mid:6c6nnolaydznkqhd+state:results]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)