Return-Path: X-Original-To: apmail-creadur-dev-archive@www.apache.org Delivered-To: apmail-creadur-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0D26911A07 for ; Wed, 17 Sep 2014 00:38:36 +0000 (UTC) Received: (qmail 23690 invoked by uid 500); 17 Sep 2014 00:38:36 -0000 Delivered-To: apmail-creadur-dev-archive@creadur.apache.org Received: (qmail 23650 invoked by uid 500); 17 Sep 2014 00:38:35 -0000 Mailing-List: contact dev-help@creadur.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@creadur.apache.org Delivered-To: mailing list dev@creadur.apache.org Received: (qmail 23637 invoked by uid 99); 17 Sep 2014 00:38:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Sep 2014 00:38:35 +0000 Date: Wed, 17 Sep 2014 00:38:35 +0000 (UTC) From: "Sebb (JIRA)" To: dev@creadur.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (RAT-179) Maven plugin and Ant task do not support adding extra approved licences MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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; 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 tag. > These are not added to the approved licenses list. > This has to be done through the 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 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)