You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2017/06/07 18:34:18 UTC

[jira] [Commented] (HBASE-18176) add enforcer rule to make sure hbase-spark / scala aren't dependencies of unexpected modules

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

Mike Drob commented on HBASE-18176:
-----------------------------------

@busbey do you have a ref to where these prior discussions came up? I tried searching list archives but couldn't locate anything.

> add enforcer rule to make sure hbase-spark / scala aren't dependencies of unexpected modules
> --------------------------------------------------------------------------------------------
>
>                 Key: HBASE-18176
>                 URL: https://issues.apache.org/jira/browse/HBASE-18176
>             Project: HBase
>          Issue Type: Improvement
>          Components: build, spark
>            Reporter: Sean Busbey
>             Fix For: 2.0.0
>
>
> We should have an enforcer plugin rule that makes sure we don't have scala and/or hbase-spark showing up in new modules. (based on prior discussions about limiting the scope of where those things show up in our classpath, esp given scala's poor history on binary compatibility)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)