tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Howard Lewis Ship <hls...@gmail.com>
Subject Re: DeprecationWarning
Date Fri, 04 Jan 2013 17:50:20 GMT
An annotation could be written, yes.  It would just produce the code I've
been manually writing.

I don't want to remove deprecated parameters because of some concern for
backwards compatibility; if we just remove the parameters, they become
informal parameters (or are just dropped), and change the behavior of
components with no warning or feedback at all.  Instead, I'm trying to
enforce one release minimum of warning before stripping them out entirely.

On Fri, Jan 4, 2013 at 4:04 AM, Denis Stepanov <denis.stepanov@gmail.com>wrote:

> Looking into 5.4 code with deprecated component parameters using the
> DeprecationWarning service and I have a few suggestions:
> Could it be implemented by introducing a new annotation
> @IgnoreDeprecatedParametersWarning({"visible", "update"}) on the component
> class or using the @DeprecatedParameter on a class field? Also, why not
> just remove deprecated parameters, are they needed for the
> DeprecationWarning service to detect the binding?
> Denis

Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message