[jdt-core-dev] Referendum about deprecation warnings

["Philippe Mulet" <Philippe_Mulet@xxxxxxx>]

We get some feedback from people complaining about deprecation warnings
they cannot fix, since they have to preserve existing APIs even after some
implementation portions got deprecated.

A typical example is:

public class X {

  /** @deprecated */
  public void foo(Y y){
     y.bar();
  }
}

/** @deprecated */
public class Y {
  public void bar(){}
}

In such a situation, the sender is itself deprecated, but still reports are
issued since its implementation uses deprecated members (bar()).

An improvement would be to ignore deprecation warnings located inside
deprecated code. We could add an option for this, or simply change the
existing behavior.
What do you think ?