java-enforce-logrecords

To enforce consistent LogRecord usage and test coverage across Java Maven modules, activate the java-enforce-logrecords workflow. It validates production logging and generates remediation plans using structured violations.

Direct logger calls should be used for DEBUG and TRACE levels, while LogRecord is enforced for INFO, WARN, ERROR, and FATAL logs. This distinction ensures consistent logging practices across Java modules.

To validate that Java LogRecord definitions are tested with LogAssert, run the enforcement workflow. It detects LogMessages classes, checks test coverage, and produces structured violations for any untested records.

The LogRecord enforcement workflow supports both single-module and multi-module Maven Java projects. It relies on a configured module mapping store to coordinate detection and apply logging standards consistently.

The Java LogRecord enforcement process generates remediation plans by detecting LogMessages classes, validating production usage against logging standards, and producing structured enforcement steps through the cui-logging workflow.

Java logging identifiers are flagged as improperly organized during validation when they violate CUI logging standards. The enforcement workflow checks identifier organization and reports violations to ensure proper structure.