Re: [jdt-core-dev] Referendum about deprecation warnings

["Darin Wright" <Darin_Wright@xxxxxxx>]

I agree that an option would be good. Perhaps the default setting should be "on" (i.e. ignore deprecated warnings inside deprecated code).

Darin

"Philippe Mulet" <Philippe_Mulet@xxxxxxx> Sent by: jdt-core-dev-admin@xxxxxxxxxxx 09/04/2002 04:07 AM Please respond to jdt-core-dev

To:        jdt-core-dev@xxxxxxxxxxx         cc:                 Subject:        [jdt-core-dev] Referendum about deprecation warnings

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 ?

_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-core-dev