Janne, 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.
Thanks, Murray ........................................................................... Murray Altheim <murray07 at altheim.com> === = = http://www.altheim.com/murray/ = = === SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = = Boundless wind and moon - the eye within eyes, Inexhaustible heaven and earth - the light beyond light, The willow dark, the flower bright - ten thousand houses, Knock at any door - there's one who will respond. -- The Blue Cliff Record
