Further questions on deprecation.

[Cantor, Scott]

On 3/4/17, 6:36 AM, "dev on behalf of Rod Widdowson" <dev-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:

> My question here is whether we can take this a step further and fire off "one shot" warning whenever a deprecated method is
> called or a deprecated class constructed?  This might get pretty noisy, and might be a whole lot of work, but it feels like it
> could be a useful thing to do.

For anything that's not being built by the Spring parsers, don't we have to do that if we want to deprecate something? I was thinking about how I would deprecate some of the authentication features I need to kill off, and I think I pretty much have to add logging to some flows or stick the warnings inside some actions.

I don't know if it's worth doing for things the parsers already warn about.

> Following on from this it might be a useful if one of the first things we did in V4 was to strip out all the deprecation and issue a
> pre-alpha.  Then all our development partners could at least prepare themselves.  Sure studying the logs will help, but not
> being able to compile concentrates the mind wonderfully..

Probably reasonable.

-- Scott