Re: [monitoring] Java version

Both good points, Romain! If anyone decides to mess with [monitoring] in the future hopefully they'll be remembered. Matt On Mon, May 20, 2013 at 11:38 AM, Romain Manni-Bucau wrote: > Hi > > you can still add the methods without @Override, it will make it happy for > both jvm. That said using

Re: [monitoring] Java version

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 * *Blog: **http://rmannibucau.wordpres

Re: [monitoring] Java version

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 wrote: > I'm looking at the [monitoring] sa

[monitoring] Java version

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 u