[RAT-179] Maven plugin and Ant task do not support adding extra approved licences

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.11
• Fix Version/s: 0.12
• Component/s: Client - ant, Client - maven
• Assignee: Philipp Ottlinger
• Reporter: Sebb
• Created: 16/Sep/14 23:12
• Updated: 19/May/15 22:25
• Resolved: 19/May/15 22:25

Description

Bug report

Users can add new license types using the <licenses> tag.

Affects: Maven- and ANT plugin

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.

Ant

Same issue for Ant task; <rat:approvedLicense/> configs replace the default set.

Reported by solomax via mail

Implementation

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

<addDefaultLicenseMatchers>false</addDefaultLicenseMatchers>

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

addDefaultLicenseMatchers = false