Example Brokk.ai-based fix of a bad logging dir on startup #5308
+78
−9
Terasology Jenkins.io / PMD
succeeded
Feb 11, 2026 in 0s
1 new issue, 180 total
| Total | New | Outstanding | Fixed | Trend |
|---|---|---|---|---|
| 180 | 1 | 179 | 0 | 👎 |
Reference build: Terasology » engine » develop #3
Details
Severity distribution of new issues
| Error | Warning High | Warning Normal | Warning Low |
|---|---|---|---|
| 0 | 1 | 0 | 0 |
Annotations
Check warning on line 285 in facades/PC/src/main/java/org/terasology/engine/Terasology.java
terasology-jenkins-io / PMD
SystemPrintln
HIGH:
Usage of System.out/err.
Raw output
References to System.(out|err).print are usually intended for debugging purposes and can remain in the codebase even in production code. By using a logger one can enable/disable this behaviour at will (and by priority) and avoid clogging the Standard out log. <pre> <code> class Foo{ Logger log = Logger.getLogger(Foo.class.getName()); public void testA () { System.out.println("Entering test"); // Better use this log.fine("Entering test"); } } </code> </pre> <a href="https://docs.pmd-code.org/pmd-doc-7.7.0/pmd_rules_java_bestpractices.html#systemprintln"> See PMD documentation. </a>
Loading