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

Hudson commented on HBASE-21282:
--------------------------------

Results for branch branch-2
        [build #1375 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1375/]: 
(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/1375//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/1375//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/1375//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


(/) {color:green}+1 client integration test{color}


> Upgrade Jetty dependencies to latest in major-line
> --------------------------------------------------
>
>                 Key: HBASE-21282
>                 URL: https://issues.apache.org/jira/browse/HBASE-21282
>             Project: HBase
>          Issue Type: Task
>          Components: dependencies
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0
>
>         Attachments: HBASE-21282.001.branch-2.0.patch
>
>
> Looks like we have dependencies on both jetty 9.2 and 9.3, but we're lagging 
> pretty far behind in both. We can upgrade both of these to the latest (august 
> 2018).
>  
> I'll also have to take a look at why we're using two separate versions (maybe 
> we didn't want to switch from jetty-jsp to apache-jsp on 9.2->9.3?). Not sure 
> if there's a good reason for this.



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

Reply via email to