Hello,
I am looking for some thoughts that allow me to decide whether I am
going to use 1.2 or 1.3 for my next project. Work starts in a few weeks
from now and needs to be finished somewhere in July. The Wicket part is
rather small (<10 crud pages) but it will feature spring annotations,
wicket-auth with Acegi (hopefully with a stateless login page), and
probably some ajax updated panels.
I see three options:
- by July wicket 1.3 is not ready for production use => 1.2 (option 1)
- by July wicket 1.3 is ready for production use =>
- it is easy to switch from 1.2 to 1.3 => 1.2 now, switch to 1.3 later
(option 2)
- it is not so easy to switch from 1.2 to 1.3 => 1.3 (option 3)
WDYT?
Regards,
Erik.
--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
