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

Hudson commented on HBASE-20656:
--------------------------------

Results for branch branch-2.0
        [build #416 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/416/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/416//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/416//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/416//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> Validate pre-2.0 coprocessors against HBase 2.0+
> ------------------------------------------------
>
>                 Key: HBASE-20656
>                 URL: https://issues.apache.org/jira/browse/HBASE-20656
>             Project: HBase
>          Issue Type: New Feature
>          Components: tooling
>    Affects Versions: 3.0.0
>            Reporter: Balazs Meszaros
>            Assignee: Balazs Meszaros
>            Priority: Major
>             Fix For: 3.0.0, 2.1.0, 2.0.1
>
>         Attachments: HBASE-20656.master.001.patch, 
> HBASE-20656.master.002.patch, HBASE-20656.master.003.patch, 
> HBASE-20656.master.004.patch, HBASE-20656.master.005.patch, 
> HBASE-20656.master.006.patch, HBASE-20656.master.007.patch, 
> HBASE-20656.master.008.patch
>
>
> We have co-processors for a while, but the API has been changed recently. We 
> should give some tooling for our users to determine if they can use the 
> previous co-processors safely or not.
> The tool should:
> - try to load the co-processors on our current classpath for ensuring class 
> references are on our classpath,
> - should check for previously removed co-processor methods.
> In this version we check only method signatures. Code references should be 
> checked in further versions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to