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

Sean Busbey edited comment on HBASE-21074 at 8/21/18 10:13 PM:
---------------------------------------------------------------

the part this change touched in 1.2 passed:

binary artifacts:
{code}
Maven details, in case our JDK doesn't match expectations:
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
2018-06-17T18:33:14Z)
Maven home: /home/jenkins/tools/maven/latest
Java version: 1.7.0_80, vendor: Oracle Corporation, runtime: 
/usr/local/asfpackages/java/jdk1.7.0_80/jre
Default locale: en_US, platform encoding: ISO-8859-1
OS name: "linux", version: "3.13.0-153-generic", arch: "amd64", family: "unix"
Do a clean building of the source artifact using code in 
/home/jenkins/jenkins-slave/workspace/HBase_Nightly_branch-1.2-AEAO7LJNYKPIH3O4GB2IR4TEIHRS6EXOJCJPGWYXWO6BFPUEZT3Q/component
Clean...
Follow the ref guide section on making a RC: Step 6 Build the source tarball
Unpack the source tarball
Diff against source tree
Checking against things we don't expect to include in the source tarball (git 
related, etc.)
Everything looks as expected.
Follow the ref guide section on making a RC: Step 8 Build the binary tarball.
Building a binary tarball from the source tarball succeeded.
{code}

jdk7:
{code}
|  +1  |    mvninstall  |   8m 17s   | the source passed 
|  +1  |       compile  |   1m 12s   | the source passed 
{code}


was (Author: busbey):
the part this change touched in 1.2 passed:

binary artifacts:
{code}
Maven details, in case our JDK doesn't match expectations:

Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
2018-06-17T18:33:14Z)

Maven home: /home/jenkins/tools/maven/latest

Java version: 1.7.0_80, vendor: Oracle Corporation, runtime: 
/usr/local/asfpackages/java/jdk1.7.0_80/jre

Default locale: en_US, platform encoding: ISO-8859-1

OS name: "linux", version: "3.13.0-153-generic", arch: "amd64", family: "unix"

Do a clean building of the source artifact using code in 
/home/jenkins/jenkins-slave/workspace/HBase_Nightly_branch-1.2-AEAO7LJNYKPIH3O4GB2IR4TEIHRS6EXOJCJPGWYXWO6BFPUEZT3Q/component

Clean...

Follow the ref guide section on making a RC: Step 6 Build the source tarball

Unpack the source tarball

Diff against source tree

Checking against things we don't expect to include in the source tarball (git 
related, etc.)

Everything looks as expected.

Follow the ref guide section on making a RC: Step 8 Build the binary tarball.

Building a binary tarball from the source tarball succeeded.
{code}

jdk7:
{code}

|  +1  |    mvninstall  |   8m 17s   | the source passed 

|  +1  |       compile  |   1m 12s   | the source passed 

{code}

> JDK7 branches need to pass "-Dhttps.protocols=TLSv1.2" to maven when building
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-21074
>                 URL: https://issues.apache.org/jira/browse/HBASE-21074
>             Project: HBase
>          Issue Type: Bug
>          Components: build, community, test
>    Affects Versions: 1.5.0, 1.2.7, 1.3.3, 1.4.7
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Major
>             Fix For: 3.0.0, 1.5.0, 1.2.7, 1.3.3, 2.0.2, 2.2.0, 2.1.1, 1.4.7
>
>         Attachments: HBASE-21074-branch-1.v0.patch
>
>
> Maven central now requires TLSv1.2 and by default JDK7 doesn't use it. So 
> anyone building from a clean repo will fail like our nightly check of 
> building the convenience binary from the source tarball e.g. 1.4
> {code}
> [INFO] Scanning for projects...
> [INFO] Downloading from apache release: 
> https://repository.apache.org/content/repositories/releases/org/apache/apache/18/apache-18.pom
> [INFO] Downloaded from apache release: 
> https://repository.apache.org/content/repositories/releases/org/apache/apache/18/apache-18.pom
>  (16 kB at 14 kB/s)
> [INFO] Downloading from Nexus: 
> http://repository.apache.org/snapshots/org/apache/felix/maven-bundle-plugin/2.5.3/maven-bundle-plugin-2.5.3.pom
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/felix/maven-bundle-plugin/2.5.3/maven-bundle-plugin-2.5.3.pom
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [ERROR] Unresolveable build extension: Plugin 
> org.apache.felix:maven-bundle-plugin:2.5.3 or one of its dependencies could 
> not be resolved: Failed to read artifact descriptor for 
> org.apache.felix:maven-bundle-plugin:jar:2.5.3 @ 
>  @ 
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]   
> [ERROR]   The project org.apache.hbase:hbase:1.4.7-SNAPSHOT 
> (/home/jenkins/jenkins-slave/workspace/HBase_Nightly_branch-1.4-EDDBHIHAYHZVAGB2FQL37O5LZNSEJJEXGP55DEGOA4FQKBLNWBAQ/unpacked_src_tarball/pom.xml)
>  has 1 error
> [ERROR]     Unresolveable build extension: Plugin 
> org.apache.felix:maven-bundle-plugin:2.5.3 or one of its dependencies could 
> not be resolved: Failed to read artifact descriptor for 
> org.apache.felix:maven-bundle-plugin:jar:2.5.3: Could not transfer artifact 
> org.apache.felix:maven-bundle-plugin:pom:2.5.3 from/to central 
> (https://repo.maven.apache.org/maven2): Received fatal alert: 
> protocol_version -> [Help 2]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerException
> {code}
> if we pass "-Dhttps.protocols=TLSv1.2" to maven then it should work for any 
> JDK7 version.



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

Reply via email to