Hi, As far as I understand, you want to move the classes so we can add checkstyle / PMD constraints, and more easily ensure every method call from an external class is synchronized. I think that's fine.
Having the 'proxy' classes sounds like a solution for the backward compatibility concerns (not the "perfect" solution, but a good solution for Jackrabbit 2). For Jackrabbit 3 I hope people will not directly cast to implementation classes any longer. Regards, Thomas
