hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-16351) do dependency license check via enforcer plugin
Date Mon, 19 Jun 2017 14:30:00 GMT

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

Mike Drob updated HBASE-16351:
    Attachment: HBASE-16351.patch

* Label error message with {{WARNING}} in aggregate license file
* Check for {{WARNING}} lines using maven enforcer using Beanshell
* Give the user a helpful build fail message with pointers on where to look instead of a stack

Manually tested failures by removing entries from supplemental-models.xml

> do dependency license check via enforcer plugin
> -----------------------------------------------
>                 Key: HBASE-16351
>                 URL: https://issues.apache.org/jira/browse/HBASE-16351
>             Project: HBase
>          Issue Type: Improvement
>          Components: build, dependencies
>            Reporter: Sean Busbey
>             Fix For: 1.4.0, 2.0.0-alpha-2
>         Attachments: HBASE-16351.patch
> As a stop-gap measure we've made our velocity template fail things when we attempt to
bundle a cat-x dependency (see HBASE-16318). Unfortunately, the error messages in this case
are non-obvious and digging to find the culprit in a partially rendered LICENSE file leaves
a lot to be desired.
> The maven enforcer plugin should allow us to fail more gracefully, with output given
on the maven console.

This message was sent by Atlassian JIRA

View raw message