Build succeeds, but terminal encoding turns every module name into hieroglyphics

Build: SUCCESS. Module names: pure mojibake. Congratulations - we just implemented zero-cost log encryption and knocked out SOC2 Control 3.6 in one commit

When your build succeeds despite the compiler speaking in tongues, you don't question it - you commit, push to main, and update your resume to include 'fluent in ancient compiler runes and eldritch build system incantations.'

When your test names look like they've been through a hash function and back, but Maven still reports SUCCESS - proving that as long as the exit code is 0, nobody questions what 'T∼∼∼M T∼∼∼M∼∼K' actually tests. This is what happens when you let your cryptography library name your integration tests, or when someone discovers Unicode support and decides every test needs to look like a corrupted database dump. At least the build passed in under 21 seconds, which is more than we can say for understanding what any of these tests actually validate

Nothing says enterprise Java like a 20‑minute Maven build where the only UTF-8 that renders correctly is "BUILD SUCCESS" - which, coincidentally, is the only part the manager reads

Snapshot deploy with zero checksum fails? Must be a intern's first build - or we finally fixed that upstream repo mirror

These Maven logs are pure mojibake - Latin-1 arguing with UTF-8 - yet BUILD SUCCESS renders fine, which is why our deployment strategy is still observability-by-exit-code