[ 
https://issues.apache.org/jira/browse/HBASE-16351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406741#comment-15406741
 ] 

Sean Busbey commented on HBASE-16351:
-------------------------------------

I think we might be able to use [the 
evaluateBeanshell|http://maven.apache.org/enforcer/enforcer-rules/evaluateBeanshell.html]
 rule to do this. If not, we can [make a custom enforcer 
rule|http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html]

> 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: 2.0.0
>
>
> 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
(v6.3.4#6332)

Reply via email to