From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Markus KARG <markus(at)headcrashing(dot)eu> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Pre-processing during build |
Date: | 2015-06-17 18:47:48 |
Message-ID: | CADK3HHKrWpwj76S5BGBxAWqZbWSK=gC0hA-tvGtQmujbmDNR4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
There is a mavenized pull here https://github.com/pgjdbc/pgjdbc/pull/322
which should make this experiment a bit eaiser
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On 17 June 2015 at 14:38, Markus KARG <markus(at)headcrashing(dot)eu> wrote:
> >When I tried it in the past (for Jaybird) I ran into problems, it might
> have been an IncompatibleClassChangeError (or subclass) on classloading
> time, but I can't remember the exact details. I tried reading the JLS and
> JVM spec on this point, but I find it hard to come to a conclusion, so I
> will try a small experiment this weekend.
>
> Let's base further discussions on your weekend's test results aka hard
> facts. :-)
>
> >However that is half of your problem. The other half is that you risk
> using classes, methods or maybe even features that are not available in a
> lower Java version and that will not be detected compile time, but only at
> runtime (and not just in newly added JDBC 4.2 methods).
>
> This can most simply be detected by a "jre6 compliance" test drive with
> explicit JRE6 runtime lib in bootclasspath.
>
> -Markus
>
>
>
> --
> 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 | Markus KARG | 2015-06-17 20:09:09 | Re: Pre-processing during build |
Previous Message | Markus KARG | 2015-06-17 18:38:26 | Re: Pre-processing during build |