You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/01/16 12:47:00 UTC

[jira] [Commented] (HBASE-23698) Switch central repo to https on branch-1

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

Hudson commented on HBASE-23698:
--------------------------------

Results for branch branch-1
	[build #1202 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1202/]: (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-1/1202//General_Nightly_Build_Report/]


(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7 report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1202//JDK7_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-1/1202//JDK8_Nightly_Build_Report_(Hadoop2)/]




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


> Switch central repo to https on branch-1
> ----------------------------------------
>
>                 Key: HBASE-23698
>                 URL: https://issues.apache.org/jira/browse/HBASE-23698
>             Project: HBase
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 1.6.0
>            Reporter: Bharath Vissapragada
>            Assignee: Bharath Vissapragada
>            Priority: Blocker
>              Labels: broken-build
>             Fix For: 1.6.0
>
>
> Maven central started enforcing https [1] today and branch-1 builds are failing presumably due to an older maven version. 
> Maven 3.2.3 [2] and later already switched the defaults, so not every one might run into this problem, depending on what mvn they are using. Jenkins jobs are hitting this, so they are likely using an older version.
> [1] https://blog.sonatype.com/central-repository-moving-to-https
> [2] https://issues.apache.org/jira/browse/MNG-5672



--
This message was sent by Atlassian Jira
(v8.3.4#803005)