Neil Bartlett wrote: > For a library, always target the lowest Java version you can possibly > get away with, because this makes your library maximally reusable. > > The difference in functionality between 5.0 and 6.0 is so miniscule, I > wonder why anybody ever asks this question. If you are really using > new APIs from Java 6.0 then you probably know about it already. If > For the API, you're right. There's some more stuff to do for testing, though: if you want to support only Java 6 (*) you just need to test with Java 6; if you are compatible with Java 5, you need to test both. Now, with tools such as Hudson this is not hard, nevertheless it's one more thing to do.
(*) It's also true that you should also test multiple JDKs (e.g. Sun's and OpenJDK) and probably we should start testing with the current builds of Java 7. Indeed, you need multi-config testing, but if you can drop at least Java 5 you cut in half your burden. -- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog [email protected] - mobile: +39 348.150.6941 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
