On Mon, 25 Apr 2016, Allison, Timothy B. wrote:
Thank you, Konstantin, for catching this. I agree about breaking changes in trunk.
We do have a check (clirr-maven-plugin) to ensure that we don't accidentally make backwards-incompatible changes on tika-core, but sadly it looks like it's disabled for those classes so we missed the warning :(
Should we plop the old classes back where they were, add deprecation and live with a bit of messiness for a few versions?
Assuming we can't re-do them to delegate through to the new-style language code, I think that's our best option
Nick
