On Tue, Jun 30, 2009 at 9:21 AM, Erik van Oosten<[email protected]> wrote: > > Correct. So its not a thing to do for 1.4 as you will have a compile error > iff you use @Override. > > Can we go back to main point now?
We are discussing the main point. You're proposing removing a method from an interface in the Wicket API without deprecating it first. I'd vote for deprecation. If there is any client code out there that uses the method, then they'll be notified via the deprecation. You have an opportunity with 1.4 to deprecate it if you want. Then, remove it for 1.5.
