I think we're saying the class files are 1.5 compatible, it's just the 1.6 run-time libs do certain (undefined) orderings differently, isn't it?
/Gwyn On Sun, May 4, 2008 at 9:40 PM, Johan Compagner <[EMAIL PROTECTED]> wrote: > But we cant build with java 6 or can we say that class files are 1.5?? > The snapshots shouldnt be suddenly 1.6 only > > > > On 5/4/08, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > Yes, and that is why I think Java 6 would be a benefit to the server: > > > > 1. to fix the tests > > 2. to make sure they stay fixed :) > > > > Martijn > > > > On 5/4/08, James Carman <[EMAIL PROTECTED]> wrote: > > > Don't the test cases fail with 1.6? > > > > > > > > > On Sun, May 4, 2008 at 12:08 PM, Martijn Dashorst > > > <[EMAIL PROTECTED]> wrote: > > > > I know we have to compile everything using Java 5. But as many of our > > > > users are running Java 6 already, perhaps we should add a testing > > > > build profile that builds Wicket using Java 6. One problem: we don't > > > > have Java 6 installed on the box. > > > > > > > > (Java 6 would also be a big improvement performance wise I think) > > > > > > > > Should we install java 6? And if so, who is going to do so? > > > > > > > > Martijn > > > > > > > > -- > > > > Buy Wicket in Action: http://manning.com/dashorst > > > > Apache Wicket 1.3.3 is released > > > > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3 > > > > > > > > > > > > > -- > > Buy Wicket in Action: http://manning.com/dashorst > > Apache Wicket 1.3.3 is released > > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3 > > >
