Skip to content
This repository has been archived by the owner on Jun 7, 2021. It is now read-only.

APEXCORE-542 - Fix debug level verbose option for Apex cli. #403

Merged
merged 1 commit into from Nov 15, 2016

Conversation

deepak-narkhede
Copy link
Contributor

This changes fixes the debug level console logging for Apex cli.

The default logger level is INFO level for Apex cli. So even if we specify the threshold level as DEBUG for ConsoleAppender, the default parent level less that the Console Appender level. Hence it is not considered for logging.
Fix is that logger level is set to DEBUG initially and threshold level for ConsoleAppender is set as per the argument passed to Apex Cli.

Note: Current two appenders are used Event and Console Appenders.

For instrumentation details and unit testing please find the attached file.
Uploading apex-cli-debug-verbose-fix.log…

apex-cli-debug-verbose-fix.txt

@deepak-narkhede
Copy link
Contributor Author

@tushargosavi, @yogidevendra. Could you please review ?

@yogidevendra
Copy link

Looks fine to me. I will wait for couple of days for the feedback from other community members and then merge this.

* is INFO level. So overiding it to DEBUG level and threshold level for Console-
* appender is set through command line arguments.
*/
logger.setLevel(Level.DEBUG);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you set it to the verbose level, instead of setting it to debug for all cases?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks ! Done. Now it will override by logLevel specified by user through Apex Cli.

@asfgit asfgit merged commit e1ada7e into apache:master Nov 15, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
4 participants