I'm not proposing that we change the source to use JDK 1.7 features (not yet, anyway).
On Thu, Jun 7, 2012 at 2:13 AM, Massimo Lusetti <[email protected]> wrote: > On Tue, Jun 5, 2012 at 6:52 PM, Howard Lewis Ship <[email protected]> wrote: > >> Interesting that that one test that fails from the command line (the >> one about template character encoding) works on JDK 1.7. >> >> There's a couple of warnings, and something's gone kablooie in the JavaDoc. >> >> My big concern is how well code generated by the JDK 1.7 compiler, >> even targeting Java 1.5, will work for end-user applications running >> on JDK 1.5 or earlier. Any insights? > > I'm sorry but I still don't have JDK 1.7 on any of my boxes. All of my > clients still run 1.6 and I have always compiled on 1.6 for 1.6 > > Cheers > -- > Massimo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
