From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Mark Rotteveel <mark(at)lawinegevaar(dot)nl> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Maven Artifact JDK Suffix |
Date: | 2016-01-15 11:56:54 |
Message-ID: | CADK3HHKap19C9=20sQpTqowY-0=43O04Vsb2_7C8gJ8FfVc9FA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On 15 January 2016 at 06:51, Mark Rotteveel <mark(at)lawinegevaar(dot)nl> wrote:
> On Fri, 15 Jan 2016 06:24:21 -0500, Dave Cramer <davecramer(at)gmail(dot)com>
> wrote:
> > I would have to agree with this. I think people will be surprised (not
> in a
> > good way) if we upgrade to java 9 and all of a sudden maven pulls down
> JDBC
> > for java 9
>
> As far as I know, starting with Java 9 this problem could be solved with
> multi-release JARs (JEP-238, http://openjdk.java.net/jeps/238) The main
> content could then be Java 8, and the Java 9 versions of classes could go
> into META-INF/versions/9 (assuming that is the final way JEP-238 will be
> realised, I am not sure if it is already in). For efficiency it would be
> best to only put in a Java 9 version of classes that really need a Java 9
> version.
>
> Yes, but in my example the customer would still be running Java 8. Does
Java 8 know how to read this jar
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
--
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Rotteveel | 2016-01-15 12:02:38 | Re: Maven Artifact JDK Suffix |
Previous Message | Mark Rotteveel | 2016-01-15 11:51:25 | Re: Maven Artifact JDK Suffix |