The difference between these two changes is though, that people can always 'fix' their code to work with the constructor change, but they might not be able to move to Java 5 due to external factors (ie they can't run on a platform with Java 5 support).
Eelco On 2/16/06, Riyad Kalla <[EMAIL PROTECTED]> wrote: > I agree with Justin, if you are already introducing a break, put them all > into 1 release. Let's say you break the constructors (I'm sorry I'm not > farmiliar exactly with what was refactored) and then a certain number of > people re-normalize ontop of it, then you break it all over again for Java > 5, just break it all at once. > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
