Neither do I.
Jan
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Freitag, 20. Juli 2018 10:15
> An: dev@ant.apache.org
> Betreff: Re: Jenkins-Builds failing
>
> Now that I checked the job's logs, I think that's true. We had this
> issue in A
Now that I checked the job's logs, I think that's true. We had this
issue in Ant too (not really against Maven repos, but HTTPS hosted
Apache infrastructure). I tried setting that property in the job, but I
too don't have the necessary authorization. I don't remember if I ever
had those permissions
My hypothesis is that Java 7 must have TLS version forced to 1.2 in order
to avoid protocol errors when downloading new binaries from Maven Central
because earlier versions are disabled [1] (and TLS 1.0 is the default in
Java 7).
Gintas
1.
https://blog.pcisecuritystandards.org/are-you-ready-for-3
Haven't checked the job, but why is this system property required to be set?
-Jaikiran
On 20/07/18 12:51 AM, Gintautas Grigelionis wrote:
> I'd like to add a Java option to Ivy builds -Dhttps.protocols=TLSv1.2 but I
> get
> This job's current authorization strategy does not permit gintas to modi
