Add golden-file regression tests for FIX42 and FIX44 code generation

[Copilot]

The code generator lacked regression tests that could catch unintended changes to generated output. FIX42 and FIX44 were chosen as the two reference dictionaries: FIX42 covers fields + messages + 38 repeating groups (no components), FIX44 covers fields + messages + components + 233 groups including nested ones.

Changes

• Golden files (src/test/resources/golden/fix42/, .../fix44/) — 1492 committed .java files generated from the real FIX42/FIX44 dictionaries (from quickfixj-messages-fix42 and quickfixj-messages-fix44), with orderedFields=true and decimalGenerated=true. These are the reference baseline.

• GoldenFileTest.java — two JUnit tests:

  • testFix42GenerationMatchesGolden — runs the generator against the real FIX42 dict, diffs every .java against golden
  • testFix44GenerationMatchesGolden — same for FIX44

  On mismatch the test fails with a precise per-file, per-line report. Missing or unexpected files are also caught.

• src/test/resources/golden/README.md — documents the golden file workflow: directory layout, what the test does, and step-by-step instructions for regenerating golden files after an intentional generator change.

• Reduced generator verbosity — logDebug in MessageCodeGenerator is now a no-op by default, suppressing the per-field, per-message, and per-component log lines during standalone use. MavenMessageCodeGenerator continues to forward debug messages to Maven's log.debug(), which is silent unless Maven is run with -X.

Updating golden files

When a generator change is intentional, regenerate the golden files by running MessageCodeGenerator directly against the two dictionaries (same parameters as the test) and commit the updated golden files alongside the generator change. See src/test/resources/golden/README.md for full instructions.

[chrjohn]

@copilot please add a readme on what to do on a generator change.

[Copilot]

@copilot please add a readme on what to do on a generator change.

Added quickfixj-codegenerator/src/test/resources/golden/README.md in commit 0e67cd6. It covers the directory layout, what GoldenFileTest does, and the step-by-step workflow for regenerating the golden files after an intentional generator change (rebuild, regenerate, diff, re-run tests, commit together).

[chrjohn]

@copilot the generator has too verbose output. We don't need to log every single generated field, message and component.

[Copilot]

@copilot the generator has too verbose output. We don't need to log every single generated field, message and component.

Fixed in commit dacfd12. logDebug in the base MessageCodeGenerator is now a no-op, so the per-field/message/component lines are no longer printed during standalone use. MavenMessageCodeGenerator still forwards to Maven's log.debug(), which is quiet by default and visible only when running with -X.