Re: RFC: Make new versions of pgjdbc Java8+ - Mailing list pgsql-jdbc

From Álvaro Hernández Tortosa
Subject Re: RFC: Make new versions of pgjdbc Java8+
Date
Msg-id 69ae857b-15cc-36dd-f380-6620ef1effb9@8kdata.com
Whole thread Raw
In response to Re: RFC: Make new versions of pgjdbc Java8+  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-jdbc


On 04/04/17 17:58, Dave Cramer wrote:

On 4 April 2017 at 11:11, Álvaro Hernández Tortosa <aht@8kdata.com> wrote:


On 03/04/17 22:53, rado@edno.moe wrote:
On 2017-04-03 23:02, Dave Cramer wrote:
On 3 April 2017 at 16:01, Álvaro Hernández Tortosa <aht@8kdata.com>
wrote:

On 03/04/17 21:15, rado@edno.moe wrote:
Hi everyone.
On 2017-04-03 21:58, Stephen Frost wrote:
Dave,

* Dave Cramer (pg@fastcrypt.com) wrote:
On 3 April 2017 at 14:33, Álvaro Hernández Tortosa
<aht@8kdata.com> wrote:
Quick eyeball of the latest two versions shows significant download
of
jre6, and a scary data of 1208 jre7. I wonder what project is using
that?

Chef.

All but ~4000 of those hits were by either "Chef Client" or "Chef
Knife", most of which were, unsurprisingly, just 304's ("not
modified").

From 100 000 downloads?
This link shows which other POMs are referring to 9.4.1208.jre7:
http://mvnrepository.com/artifact/org.postgresql/postgresql/9.4.1208.jre7/usages
[1]
Keep in mind that I don't know how reliable is this data, but Clojure
and Spring Boot are quite popular projects.

     This doesn't seem to happen with current version 42:

http://mvnrepository.com/artifact/org.postgresql/postgresql/42.0.0.jre7/usages
[2] (not used so far)

The big projects that embed jdbc drivers are not so many and probably they are not releasing new versions only because of the dependencies updates. And the 42.0.0 release is quite new.

As a side note: Hibernate 5.2 is officially Java8 only: https://github.com/hibernate/hibernate-orm/wiki/Migration-Guide---5.2#move-to-java-8-for-baseline
And they soon will drop support for 5.1 (http://in.relation.to/2017/03/14/hibernate-orm-515-final-release/) when 5.3 is released. They've changed their policy last year and now you get bug fixes only for the current and the previous release.
The upcoming version of Spring platform is also Java8: https://github.com/spring-projects/spring-framework/wiki/What%27s-New-in-the-Spring-Framework#whats-new-in-spring-framework-5x
Spring 4.x is Java6, but Spring Boot requires Java7 and recommends Java8: http://docs.spring.io/spring-boot/docs/1.5.2.RELEASE/reference/htmlsingle/#getting-started-system-requirements

IMO these two will drive some migration effort to Java8.

    Agreed. Very interesting. I think we should also "recommend" our users to move forward. I don't see someone willing to upgrade to PostgreSQL 10 but not willing to update the JRE (it's either both or none, and if it is none, they are well served with existing drivers).

    So what do we do? I can still develop SCRAM for either version of Java (and while I have already expressed my preference, I will do it even for Java6, if that's the decision) :) I'm not a committer, so committers: please let me know what would be the "official" final decision. Thanks,



Keep going with java 8 for now. Given that the use of MD5 the way we actually use it is not really an issue, I'm less worried about this than I originally thought. I do have some feelers out in the enterprise though to get some feed back

    Great, I will do that.

    If, then, at some point we get strong feedback, I'd volunteer to help backport the code to Java6/7.


    Cheers,

    Álvaro


-- 

Álvaro Hernández Tortosa


-----------
<8K>data

pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: Re: RFC: Make new versions of pgjdbc Java8+
Next
From: Vladimir Gordiychuk
Date:
Subject: Re: Logical Replication: adjacent COMMIT messages with thewrong StartLSN