Oh, but I *am* using JDK6 with Click. But I use the provided jars instead of the sources provided by Click. The libs are obviously compiled with 1.4 to be compatible. If I want to run Click as "native" JDK6, I would have to include the sources in my project and compile them myself.
But I don't know if I want that. Should I? On Thu, 2009-04-16 at 18:36 +0000, Freddy Daoud wrote: > Hi all, > > Just my 2c. It is important to distinguish the advantages > *in the Click API* of using JDK5 features from the advantages > of using JDK5 yourself. So reasons like: > > - JDK1.4 has reached EOL in October 2008 so people could have seen it > coming. > - JDK 5 has been available for a long time, and even THAT will reach > EOL, as per October 2009) > - JDK 6 is much faster :) > > are not valid IMHO. What I mean by that, is that Click does not > *require* JDK1.4 - it is merely compatible with it. There's nothing > stopping *you* from using JDK6 with Click and taking advantage of > everything said above. The only difference is when you deal with > the Click API - you won't get generified collections for example, > so you'll get warnings and so on. So indeed that's where I agree > that for example the proper use of generics and annotations in a > JDK5 version of Click would help. > > Cheers, > Freddy > > WarnerJan Veldhuis QPR CostControl BV Clarissenhof 15 4133 AB Vianen Tel: +31(0)347 355023 Helpsdesk: +31(0)347 355027
