creadur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philipp Ottlinger (JIRA)" <>
Subject [jira] [Updated] (RAT-179) Maven plugin and Ant task do not support adding extra approved licences
Date Mon, 20 Apr 2015 21:39:59 GMT


Philipp Ottlinger updated RAT-179:
    Attachment: RAT-179.tar.gz

[~solomax] Is your expectation that the attached project is scanned and goes through?

It contains:
* ASF2.0 and MIT (should be part of the defaults)
* MIT and GPL (self-defined, added via pom.xml)

Thanks for your feedback

> Maven plugin and Ant task do not support adding extra approved licences
> -----------------------------------------------------------------------
>                 Key: RAT-179
>                 URL:
>             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|]

This message was sent by Atlassian JIRA

View raw message