[ https://issues.apache.org/jira/browse/RAT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136581#comment-14136581 ]
Sebb commented on RAT-179: -------------------------- Same issue for Ant task; <rat:approvedLicense/> configs replace the default set. > 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 > Reporter: Sebb > > Users can add new license types using the <licenses> tag. > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)