Check my last comment on SOLR-215
which should not be an indication that the code in question will not
function correctly. Also, there isn't a peep of warning in CHANGES.txt
I was waiting for SOLR-360 to add the CHANGES.txt for multi-core related
things. You are right, the deprecated API deprecations and alternatives
need to go in ASAP.
The problem seems to stem from leaving in the old method. Since we are
breaking backward compatibility, it would be better to break hard and
prevent Solr from compiling, or to actually provide backward compatiblity.
grumpy,
-Mike
I think there is a way to maintain backward compatibility, but it is not
totally straightforward (so i can't do it right now)
Sorry this caused you head banging and thanks for (unwhittingly) helping
to iron out SOLR-215.
ryan
