I'm also in favour or removing, but maybe do it as a two phase approach, first drop the code but leave a dummy component that will log a warning in case the specific index type is used, next on phase 2 drop the warning.
On Thu, Dec 10, 2015 at 12:36 PM, Chetan Mehrotra <[email protected] > wrote: > Given that ordered property indexes have been deprecated long time > back it would be better if we remove the corresponding code or at > least disable the OSGi components for it > > I would prefer removal of code as otherwise we need to take care of > that code also if any cross cutting refactoring is to be performed > (say some change which touch all indexes) > > Thoughts? > > Chetan Mehrotra >
