commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: [monitoring] Java version
Date Mon, 20 May 2013 16:38:29 GMT
Hi

you can still add the methods without @Override, it will make it happy for
both jvm. That said using proxies is another solution which works better in
general for such cases IMO.

*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*



2013/5/20 Matt Benson <gudnabrsam@gmail.com>

> Hrm, actually I misspoke.  I was thinking of the breaking JDBC changes in
> Java 7.  Same difference except I'm not willing to push [monitoring] that
> far yet.  Disregard and I'm building with Java 6 :P
>
> Matt
>
>
> On Mon, May 20, 2013 at 10:06 AM, Matt Benson <gudnabrsam@gmail.com>
> wrote:
>
> > I'm looking at the [monitoring] sandbox component.  (Notwithstanding some
> > complex approach) it can't be built with a JDK > 1.5 due to the interface
> > additions made to JDBC in Java 1.6.  As 1.5 is EOL and this is a sandbox
> > component that may well never see the light of day anyway, any objections
> > to upgrading to 1.6 and adding the missing methods to the JDBC
> > implementations so we can at least built the thing simply?
> >
> > Matt
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message