I did a migration from 1.3.7 to 6.18 quite recently (main project plus shared sub-module). I found the process quite simple really and it was an opportunity to revisit some very poorly constructed code. My main problem wasn't so much with the migration itself but with my colleagues' code. Clearly the majority have very little understanding of the overall 'Wicket philosophy', the most egregious failing being a complete lack of understanding of the power of Wicket models and the pull model.
This could also be an opportunity for you to take a step back and re-evaluate a lot of decisions both technical and functional (which regrettably wasn't possible in my case). Maybe Wicket isn't suitable for you anymore or maybe the rest of your project could use an architectural rethink. Good luck whatever you choose! CN -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Upgrading-Wicket-1-2-site-tp4671909p4671924.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
