Re: Antlib SVN and antunit Java versions

2018-12-20 Thread Jaikiran Pai


On 19/12/18 11:29 PM, Stefan Bodewig wrote:
> On 2018-12-18, Jaikiran Pai wrote:
>
>> One option in similar cases that we have employed in other jobs is to
>> configure the Java system property -Dhttps.protocols to "TLSv1.2". But
>> this version of TLS is only supported in a Java release after Java 1.5.
> I'd be in favor of updating the jobs. Nobody would build releases using
> Java 1.5 either, I guess.
Done. I have updated the jobs of antlib svn and antunit to use Java 8 to
build it.

>
>> At a more higher level, I think it's probably time to decide whether we
>> want to change the minimum required Java versions for these libraries?
>> Should we now mandate Java 1.8 at least?
> In the case of antlib svn we could simply decide to call it dead or
> dormant or whatever (like almost all other antlibs, I guess). Unless I'm
> overlooking something, the svn antlib is neither listed on
> http://ant.apache.org/antlibs/proper.html nor
> http://ant.apache.org/antlibs/sandbox.html - so it doesn't even exist
> from out user's point of view.
I found this (live) page http://ant.apache.org/antlibs/svn/ the other
day while looking at the Jenkins failure. But now that you mention it, I
don't remember how I landed up on that page. I don't see it linked in
the Jenkins job or some other place. But yes, I don't see it linked
anywhere in the Ant website. I'll start a new VOTE thread to retire this
project. I might need Jan's help here if/after the VOTE passes to
actually do some of the process involved in retiring projects.

-Jaikiran




-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



Re: Antlib SVN and antunit Java versions

2018-12-19 Thread Stefan Bodewig
On 2018-12-18, Jaikiran Pai wrote:

> One option in similar cases that we have employed in other jobs is to
> configure the Java system property -Dhttps.protocols to "TLSv1.2". But
> this version of TLS is only supported in a Java release after Java 1.5.

I'd be in favor of updating the jobs. Nobody would build releases using
Java 1.5 either, I guess.

> At a more higher level, I think it's probably time to decide whether we
> want to change the minimum required Java versions for these libraries?
> Should we now mandate Java 1.8 at least?

In the case of antlib svn we could simply decide to call it dead or
dormant or whatever (like almost all other antlibs, I guess). Unless I'm
overlooking something, the svn antlib is neither listed on
http://ant.apache.org/antlibs/proper.html nor
http://ant.apache.org/antlibs/sandbox.html - so it doesn't even exist
from out user's point of view.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



Re: Antlib SVN and antunit Java versions

2018-12-18 Thread Gintautas Grigelionis
On Tue, 18 Dec 2018 at 10:44, Dominique Devienne 
wrote:

> On Tue, Dec 18, 2018 at 9:21 AM Jaikiran Pai  wrote:
>
> > [...] 2 jobs[1][2] which are for Antlib SVN and Antunit libraries.
>
> Both these jobs are configure for JDK 5 [...]
> > However, the Maven central repo [...[ has been configured not to let
> > clients with
> > lower TLS versions (lesser than TLSv1.2) to communicate with it. [...]
>
> But this version of TLS is only supported in a Java release after Java 1.5.
> > [...]
>
> Should we now mandate Java 1.8 at least?
> >
>
> Sounds completely reasonable to me. Thanks for the clear message. +1. --DD
>

I'd say the choices are:

   -  use Java 6 or 7 with command line switch forcing TLSv1.2 or Java 8
   and crosscompile to Java 5
   -  change to Java 8 to follow Ant 1.10

Java 9+ can only crosscompile to Java 6+. It will be interesting to see if
JEP 332 [1] gets backported...

Gintas

[1] https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8202625


Re: Antlib SVN and antunit Java versions

2018-12-18 Thread Dominique Devienne
On Tue, Dec 18, 2018 at 9:21 AM Jaikiran Pai  wrote:

> [...] 2 jobs[1][2] which are for Antlib SVN and Antunit libraries.

Both these jobs are configure for JDK 5 [...]
> However, the Maven central repo [...[ has been configured not to let
> clients with
> lower TLS versions (lesser than TLSv1.2) to communicate with it. [...]

But this version of TLS is only supported in a Java release after Java 1.5.
> [...]

Should we now mandate Java 1.8 at least?
>

Sounds completely reasonable to me. Thanks for the clear message. +1. --DD