[
https://jira.codehaus.org/browse/MLICENSE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=299039#comment-299039
]
Tony Chemit edited comment on MLICENSE-37 at 5/17/12 12:48 PM:
---------------------------------------------------------------
There is two new parameters includedLicenses (whitelist) and excludedLicense
(blacklist) to deal with this.
If failIfWarning is set on then build will fail, otherwise just some warning
will be printed in console.
[see rev 16634 for
includedLicenses|https://fisheye.codehaus.org/changelog/mojo?cs=16634]
was (Author: tchemit):
There is two new parameters includedLicenses (whitelist) and
excludedLicense (blacklist) to deal with this.
If failIfWarning is set on then build will fail, otherwise just some warning
will be printed in console.
[rev 16634|https://fisheye.codehaus.org/changelog/mojo?cs=16634]
> Make it possible to restrict which licenses are allowed in a project
> --------------------------------------------------------------------
>
> Key: MLICENSE-37
> URL: https://jira.codehaus.org/browse/MLICENSE-37
> Project: Mojo's License Maven Plugin
> Issue Type: Improvement
> Affects Versions: 1.1
> Environment: Maven 3
> Reporter: Alix Warnke
> Assignee: Tony Chemit
> Fix For: 1.1
>
>
> It is currently possible to have a property, "failIfWarning", set to require
> license information for all 3rd party dependencies but there is no way to
> forbid 3rd party artifacts with a certain license.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
