Log warning for deprecated config?

[Misagh Moayyed]

OK. I may have to file one, because I don't see anything in my idp logs.
Assuming messages would show up under "net.shibboleth.idp", all I see is:
"2015-05-01 11:51:09,359 - DEBUG
[net.shibboleth.idp.attribute.resolver.spring.AttributeResolverServiceStra
tegy:64] - Creating Attribute Resolver ShibbolethAttributeResolver with 4
Attribute Definition(s), 1 Data Connector(s) and 3 Principal Connector(s)"


But no warnings. 

-----Original Message-----
From: dev [mailto:dev-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Friday, May 1, 2015 11:43 AM
To: Shib Dev
Subject: Re: Log warning for deprecated config?

On 5/1/15, 2:40 PM, "Misagh Moayyed" <mmoayyed at unicon.net> wrote:

>Hello,
>I understand components and definitions in v2 that deal with principal
connectors and nameid encoders still continue to work in v3, albeit they
are deprecated. Great!
> 
>I am however, wondering if it would make sense of the idp to issue WARN
level logs when it find these deprecated elements in the config, so a
deployer would be made aware. In practice, I suppose warnings in the log
would be easier during an upgrade to deal with, rather than cross checking
with the wiki and/or release notes (which do outline deprecated items
perfectly fine, I might add)

There are lots of warnings like that throughout the system, and if any are
missing, that's a bug.

-- Scott

-- 
To unsubscribe from this list send an email to
dev-unsubscribe at shibboleth.net