> > oh, i didn't realize this neither...so in this case i'm rather against > > this release. > > if it's not too late, i would vote -1 and remove this method from the > > interface again, but leave it in the abstract pm. so users could cast > > to abstract pm if they need it. > > > The release was already pushed out to the central Maven repository and > pulling it back would be a bit troublesome. How about if we treated > this as a regression and fixed it ASAP (next week) in 1.4.4? ok for me. i created a new issue https://issues.apache.org/jira/browse/JCR-1556.
-- toby
