You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2017/09/22 16:27:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Sean Busbey updated HBASE-18176:
--------------------------------
    Fix Version/s:     (was: 2.0.0-alpha-2)

> 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
>             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
(v6.4.14#64029)