hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18176) add enforcer rule to make sure hbase-spark / scala aren't dependencies of unexpected modules
Date Tue, 20 Jun 2017 13:53:00 GMT

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

Hudson commented on HBASE-18176:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3228 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3228/])
HBASE-18176 Enforce no scala outside hbase-spark (busbey: rev 270f317727ddb0395f3a9b3f23eeb7f978c6e6fc)
* (edit) hbase-spark/pom.xml
* (edit) 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)

Mime
View raw message