[
https://issues.apache.org/jira/browse/HBASE-18176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427896#comment-16427896
]
stack commented on HBASE-18176:
-------------------------------
Reverted from branch-2/2.0.0 by HBASE-18817
> 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
> Assignee: Mike Drob
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-18176.patch, HBASE-18176.v2.patch
>
>
> 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
(v7.6.3#76005)
