With 2.7.0-alpha-1 (nee 2.8.0-alpha-1) the PageRenamer class was replaced with a new version (understandable as due to copyright issues), but the new one is now in a different package designation, moving it from old com.ecyrd.jspwiki.PageRenamer to a new package as com.ecyrd.jspwiki.content.PageRenamer. This causes all existing code prior to 2.7 to break, forcing implementors to choose between the pre- and post-change version that seems unnecessary. Is there any reason why PageRenamer should be in .content. other than "aesthetics"? Breaking the API in this way will cause me to have two separate implementations of all my code. I understand some APIs are expected to be changing but this one seems somewhat unnecessary.
The functionality of the class changed as well, which is why it was moved. I also wanted to make sure that developers will notice this and adapt their code accordingly. The API looks deceptively similar.
I also figured that nobody uses this class. Looks like I was wrong in that regard as well.
This can be moved back, if necessary. But be warned: it is a different implementation!
/Janne
