And if develop now something to get it into production in a few months you should stick to 1.2
But if it does take longer you could use trunk. It is now a fast moving target.
But many of those changes are java 5 related and that is no behaviour change.. So that shouldn't affect at all.
as far as i can see now there is only one big code change: Converters that would affect the compile of code.
For the rest only the default change of another kind of pagemap/session store is what needs to be tested
but there are people that already tested that when it was in a branch (the clientsidestate branch)
So currently the changes looks big, but when we do the constructor change the effect will be much bigger.
Who is going to do that?
johan
On 5/21/06,
Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Hi all,
We made a branch about two days ago for Wicket 1.2, which we'll use
for maintaining 1.2. Trunk/ Head will be used for Wicket 2.0, and will
be highly experimental for a while. What's currently in there can't
even be used at all until we finish converting to generics.
So, if you were working on head/ trunk, it's probably a good idea to
either start working with distributions or on the 1.2. branch from now
on. Sorry we didn't communicate this earlier.
Regards,
Eelco
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmdlnk&kid0709&bid&3057&dat1642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
