Bug#300753: Success for jdbc3

[Markus Schaber]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig660FD6DD00913C38059C1AD1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi, Wolfgang,

If all free java sdks implement jdbc3, I don't see any real reason to
provide jdbc2 builds at all. AFAIK, JDBC standards are meant to be
compatible for older clients, so every jdbc2 app should work fine
against jdbc3 implementations.

Alternatively, what do you think about having a libpg-jdbc3-java and
libpg-jdbc2-java, the first one beeing in main. We could then obsolete
libpg-java and make it a virtual package depending on both of them, this
would also solve bug #275417 in an elegant way :-)

> I had success with using gcj-3.4 as it's based on an older gnu classpath
> release. Maybe try against gcj-3.3 or gcj-3.4 - don't know at which
> JDBC level they are. Give them a try :-)

Okay, I'll do so. But this might lead into a difficult build environment
setup including conflicts etc. :-(

Markus

-- 
Markus Schaber - http://schabi.de/

But hey!, Standard compliance is something we should strive for, so
let's try and change the Standard :-) [Alexandre Oliva, GCC Developer]

--------------enig660FD6DD00913C38059C1AD1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCSmXX6IhVmcufrl4RA8joAJ9L0JoMEK6RZLXD+k/8o9LN/5vXMwCgkWSG
d+22Jt55J9a+3c5p81g89Hg=
=Wxis
-----END PGP SIGNATURE-----

--------------enig660FD6DD00913C38059C1AD1--