Hi Simon,
yes, I didn’t face any issue like that when I released the
2.0.0-M11.
Does it work now for you?
Mit freundlichen Grüßen / Best regards
Achim Kraus
(INST/ECS4)
Bosch Software Innovations GmbH | Stuttgarter Straße 130 | 71332 Waiblingen |
GERMANY | www.bosch-si.com
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr. Stefan Ferber, Michael Hahn
From: cf-dev-bounces@xxxxxxxxxxx <cf-dev-bounces@xxxxxxxxxxx>
On Behalf Of Simon Bernard
Sent: Donnerstag, 19. Juli 2018 12:07
To: Californium (Cf) developer discussions <cf-dev@xxxxxxxxxxx>
Subject: [cf-dev] Jenkins release build failed : Received fatal alert: protocol_version
Hi californium committers,
I faced some issues releasing Leshan during deploy phase:
[ERROR] Failed to execute goal on project leshan-core-cf:
Could not resolve dependencies for project org.eclipse.leshan:leshan-core-cf:bundle:1.0.0-M8:
Failed to collect dependencies at org.eclipse.californium:californium-core:jar:2.0.0-M11:
Failed to read artifact descriptor for org.eclipse.californium:californium-core:jar:2.0.0-M11:
Could not transfer artifact org.eclipse.californium:californium-core:pom:2.0.0-M11 from/to central (https://repo.maven.apache.org/maven2):
Received fatal alert: protocol_version -> [Help 1]
After searching, it seems that sonatype does not allow TLS1.0/1.1 anymore :
https://central.sonatype.org/articles/2018/May/04/discontinued-support-for-tlsv11-and-below/
Leshan project was affected as we are using jdk7 to build.
I fixed this by adding -Dhttps.protocols=TLSv1.2 to the JVM Options of my deploy maven build step.
I just shared this information here as I know we are using jdk7 too.
@Achim, you didn't face this issue when you released the 2.0.0-M11 ? I looked at the jenkins job and I didn't see anything like this.
Simon