creadur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philipp Ottlinger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RAT-179) Maven plugin and Ant task do not support adding extra approved licences
Date Tue, 19 May 2015 22:17:01 GMT

     [ https://issues.apache.org/jira/browse/RAT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Philipp Ottlinger updated RAT-179:
----------------------------------
    Description: 
h2. Bug report
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]

h2. Implementation

h3. Maven
You can add new approved licenses by setting
{{licenses}} and {{licenseFamilies}} when configuring the apache-rat-maven-plugin.

Default licenses are approved in addition to any new licenses. If you do not want this behaviour
set
{code}
<addDefaultLicenseMatchers>false</addDefaultLicenseMatchers>
{code} 

h3. Ant
Ant seems to have worked in version 0.11 as attached project indicates.
If you do not want to add the default license matchers, set
{code}
addDefaultLicenseMatchers = false
{code}

  was:
h2. Bug report
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]

h2. Implementation

You can add new approved licenses by setting
{{licenses}} and {{licenseFamilies}} when configuring the apache-rat-maven-plugin.

Default licenses are approved in addition to any new licenses. If you do not want this behaviour
set
{code}
<addDefaultLicenseMatchers>false</addDefaultLicenseMatchers>
{code} 

Ant seems to have worked in version 0.11 as attached project indicates.


> 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, rat-179.zip
>
>
> h2. Bug report
> 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]
> h2. Implementation
> h3. Maven
> You can add new approved licenses by setting
> {{licenses}} and {{licenseFamilies}} when configuring the apache-rat-maven-plugin.
> Default licenses are approved in addition to any new licenses. If you do not want this
behaviour set
> {code}
> <addDefaultLicenseMatchers>false</addDefaultLicenseMatchers>
> {code} 
> h3. Ant
> Ant seems to have worked in version 0.11 as attached project indicates.
> If you do not want to add the default license matchers, set
> {code}
> addDefaultLicenseMatchers = false
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message