Al Maw wrote >I don't want to do any of A, B or C.
I am not a developer of wicket and it's completely up to yours how you do it, but why not the following way: 1. Keep Wicket 2 and do the constructor change there. Now you have a java 1.4 branch (wicket 1.x) and a java 5 branch (wicket 2.0 or call the thing wicket 1.5 or whatever). The very most of Wicket 2 users will not have big trouble to change the constructor. Do the packet name change in 2.0. It's easy to replace "wicket...." with "org.apache.wicket..." 2. Create a branch from 2.0 and call it 1.4. Remove all generic stuff. So you have a Java 1.4 version with classic constructor and without generics but the code is equivalent to 2.0 3. Now you have two branches that are based on the same codeline and backporting from 2.0 to 1.4 is easy. Create new features in wicket 2 and backport them (just drop the generics and add some type casts) to 1.4. 4. You can release current 1.3 as a beta and release it soon as it is. Stefan Lindner
<<winmail.dat>>
------------------------------------------------------------------------- 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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
