[
https://issues.apache.org/jira/browse/HBASE-18176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055797#comment-16055797
]
Hudson commented on HBASE-18176:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-2.0 #76 (See
[https://builds.apache.org/job/HBase-2.0/76/])
HBASE-18176 Enforce no scala outside hbase-spark (busbey: rev
4aa7ce399e28ddfd9af89fc6de2361daa4707141)
* (edit) pom.xml
* (edit) hbase-spark/pom.xml
* (edit) hbase-assembly/pom.xml
> 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: 2.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)
