Whenever using a log level, one should check if the loglevel is actually enabled, or otherwise skip the associate String creation and manipulation. An alternative to checking the log level are substituting parameters, formatters or lazy logging with lambdas. The available alternatives depend on the actual logging framework. GuardLogStatement (Priority: 1, Ruleset: Best Practices) https://docs.pmd-code.org/pmd-doc-7.0.0-rc4/pmd_rules_java_bestpractices.html#guardlogstatement

Whenever using a log level, one should check if the loglevel is actually enabled, or otherwise skip the associate String creation and manipulation. An alternative to checking the log level are substituting parameters, formatters or lazy logging with lambdas. The available alternatives depend on the actual logging framework. GuardLogStatement (Priority: 1, Ruleset: Best Practices) https://docs.pmd-code.org/pmd-doc-7.0.0-rc4/pmd_rules_java_bestpractices.html#guardlogstatement

Whenever using a log level, one should check if the loglevel is actually enabled, or otherwise skip the associate String creation and manipulation. An alternative to checking the log level are substituting parameters, formatters or lazy logging with lambdas. The available alternatives depend on the actual logging framework. GuardLogStatement (Priority: 1, Ruleset: Best Practices) https://docs.pmd-code.org/pmd-doc-7.0.0-rc4/pmd_rules_java_bestpractices.html#guardlogstatement

Whenever using a log level, one should check if the loglevel is actually enabled, or otherwise skip the associate String creation and manipulation. An alternative to checking the log level are substituting parameters, formatters or lazy logging with lambdas. The available alternatives depend on the actual logging framework. GuardLogStatement (Priority: 1, Ruleset: Best Practices) https://docs.pmd-code.org/pmd-doc-7.0.0-rc4/pmd_rules_java_bestpractices.html#guardlogstatement

Whenever using a log level, one should check if the loglevel is actually enabled, or otherwise skip the associate String creation and manipulation. An alternative to checking the log level are substituting parameters, formatters or lazy logging with lambdas. The available alternatives depend on the actual logging framework. GuardLogStatement (Priority: 1, Ruleset: Best Practices) https://docs.pmd-code.org/pmd-doc-7.0.0-rc4/pmd_rules_java_bestpractices.html#guardlogstatement

Whenever using a log level, one should check if the loglevel is actually enabled, or otherwise skip the associate String creation and manipulation. An alternative to checking the log level are substituting parameters, formatters or lazy logging with lambdas. The available alternatives depend on the actual logging framework. GuardLogStatement (Priority: 1, Ruleset: Best Practices) https://docs.pmd-code.org/pmd-doc-7.0.0-rc4/pmd_rules_java_bestpractices.html#guardlogstatement

Whenever using a log level, one should check if the loglevel is actually enabled, or otherwise skip the associate String creation and manipulation. An alternative to checking the log level are substituting parameters, formatters or lazy logging with lambdas. The available alternatives depend on the actual logging framework. GuardLogStatement (Priority: 1, Ruleset: Best Practices) https://docs.pmd-code.org/pmd-doc-7.0.0-rc4/pmd_rules_java_bestpractices.html#guardlogstatement

Whenever using a log level, one should check if the loglevel is actually enabled, or otherwise skip the associate String creation and manipulation. An alternative to checking the log level are substituting parameters, formatters or lazy logging with lambdas. The available alternatives depend on the actual logging framework. GuardLogStatement (Priority: 1, Ruleset: Best Practices) https://docs.pmd-code.org/pmd-doc-7.0.0-rc4/pmd_rules_java_bestpractices.html#guardlogstatement

Whenever using a log level, one should check if the loglevel is actually enabled, or otherwise skip the associate String creation and manipulation. An alternative to checking the log level are substituting parameters, formatters or lazy logging with lambdas. The available alternatives depend on the actual logging framework. GuardLogStatement (Priority: 1, Ruleset: Best Practices) https://docs.pmd-code.org/pmd-doc-7.0.0-rc4/pmd_rules_java_bestpractices.html#guardlogstatement

Whenever using a log level, one should check if the loglevel is actually enabled, or otherwise skip the associate String creation and manipulation. An alternative to checking the log level are substituting parameters, formatters or lazy logging with lambdas. The available alternatives depend on the actual logging framework. GuardLogStatement (Priority: 1, Ruleset: Best Practices) https://docs.pmd-code.org/pmd-doc-7.0.0-rc4/pmd_rules_java_bestpractices.html#guardlogstatement

This version of the CodeQL Action was deprecated on January 18th, 2023, and is no longer updated or supported. For better performance, improved security, and new features, upgrade to v2. For more information, see https://github.blog/changelog/2023-01-18-code-scanning-codeql-action-v1-is-now-deprecated/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-java@v3, pmd/pmd-github-action@v1, github/codeql-action/upload-sarif@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.