deprecation warnings only at TRACE log level?

[Cantor, Scott]

> <shrug>. Guess I'll find out when I update to idp 5, I sure don't see any at
> all for a couple, and the others I don't think are the ones being logged.

Only guess then is that the logging code is actually what's calling the APIs, so turning up the logging level executes some block of code that isn't otherwise running.

It's definitely impossible that it's not logging something at WARN unless TRACE is used but if there's a whole section of code guarded with an "isTraceEnabled()" call, that would explain it.

TRACE isn't heavily used so possible it escaped notice.

-- Scott