I forget what our exact rules are for this. I know that we won't break API in a point release (i.e. 1.4.8). But, what about the following scenarios? I can add these to a point release, right?
1. Add a class. In this example, I could add a class that is a custom subclass of WebRequestCycle that someone can subclass to handle runtime exceptions in Ajax differently than they do on regular requests. (i.e. they would rather not redirect on an Ajax error, but instead would like to send some JS back in a normal Wicket AJAX response) 2. Add an interface and some associated functionality. In this example, I might have an interface to add, and some additional functionality that only operated on instances of that interface. No functionality would change for existing interfaces. Those would both be okay, right? -- Jeremy Thomerson http://www.wickettraining.com
