[
https://issues.apache.org/jira/browse/PARQUET-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandor Kollar updated PARQUET-1351:
-----------------------------------
Summary: Bump java source and target to java8 for parquet-format (was:
Bump java source and target to java8)
> Bump java source and target to java8 for parquet-format
> -------------------------------------------------------
>
> Key: PARQUET-1351
> URL: https://issues.apache.org/jira/browse/PARQUET-1351
> Project: Parquet
> Issue Type: Bug
> Components: parquet-format
> Reporter: Nandor Kollar
> Assignee: Nandor Kollar
> Priority: Major
>
> parquet-format Travis builds are failing with (see for example
> [this|https://travis-ci.org/apache/parquet-format/builds/400272129?utm_source=github_status&utm_medium=notification]
> build):
> {code}
> [ERROR] Plugin org.apache.maven.plugins:maven-remote-resources-plugin:1.5 or
> one of its dependencies could not be resolved: Failed to read artifact
> descriptor for
> org.apache.maven.plugins:maven-remote-resources-plugin:jar:1.5: Could not
> transfer artifact
> org.apache.maven.plugins:maven-remote-resources-plugin:pom:1.5 from/to
> central (https://repo.maven.apache.org/maven2): Received fatal alert:
> protocol_version -> [Help 1]
> {code}
> After some investigation, I suspect that the problem is that parquet-format
> is built against JDK 1.7.0_80 (see in the logs of the failing job above), the
> default version of TLS for this JDK seems to be TLSv1 (see
> [here|https://blogs.oracle.com/java-platform-group/diagnosing-tls,-ssl,-and-https]),
> and Maven central dropped support TLS 1.1 and TLS 1.0 (see
> [here|https://lists.apache.org/thread.html/%3CCAMk_Beg9=QE-UB10c=yM8NKWiAk=bak2n3da0pgyxdfhf3w...@mail.gmail.com%3E]
> and
> [here|https://stackoverflow.com/questions/50824789/why-am-i-getting-received-fatal-alert-protocol-version-or-peer-not-authentic]).
> Despite this problem could be fixed by adding a parameter to use newer TLS
> version, I recommend bumping source and target to java8 instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
