This repository was archived by the owner on Feb 26, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
Revise logging severities #1586
Description
Activity
Actually we used bad name for the log level in the functional test projects... 0a23034 Since there was no log level with such name, we fall back to the default,
DEBUG. However, i do not think it is fair to pollute the clients' terminal with debug messages by default. I opened #1588 for that. @yDelouis WDYT?I agree and merged your PR.
Please, provide a new PR to fix the code where we used wrong log levels.It turned out we log with appropriate severities, the problem was 0a23034.
We are logging lots of things with
WARNINGpriority, which maybe not reasonable. For example we log the found manifest and content; claimed annotations and elements; and generated classes withWARNINGlog level. I think this should be definitely notWARNING(butINFO), since there is nothing to warn about, these are happening always normally.