My interpretation of Martin's comment is that using deprecation for
things that aren't actually broken just means that people will live
with lots of deprecation warnings in their code for years to
come. This could be a perfect case for introducing a weaker
alternative to deprecation, saying "here's something better that you
should really be using for new code" -- e.g. ArrayList vs. Vector. I
remember the Guava team talking about that a lot. Don't know if they
ever implemented it.
OK. But we really do need a way to do that.
Doesn't enhanced deprecation [1] in 9 cover that?
Best regards,
Vladimir Ivanov
[1] http://openjdk.java.net/jeps/277
