Message classes should not be built if spec did not change

[chrjohn]

There are FIX*.xml spec files in ./quickfixj-messages/ and its subdirectories. When building, fields and message classes will be generated based off these specs. However, even if that spec does not change, the classes will be built again even if we don't do a clean.

We should use mojohaus build-helper:uptodate-property or similar plugin to only build if the spec changed.

[chrjohn]

@jetbrains-junie please create a PR for this.

[jetbrains-junie[bot]]

Hey, it’s Junie by JetBrains! I started processing your request 🚀

[jetbrains-junie[bot]]

✅ Generation Status

• Code generation was successful

Message:

The build-helper:uptodate-property plugin was added to prevent rebuilding message classes unless the FIX spec XML files change, and Maven profiles were created for each FIX version to conditionally include code generation executions. The implementation was completed and submitted.

---

📌 Issues Detected During Processing

• Some issues occurred that may have limited the context available during generation.
• These did not prevent the operation, but fixing them could improve the results.

Message:

❌ I tried to build the project before getting started, but it didn’t work.

There might be issues with the environment or the code itself. Please check build log for more details.

More information:

• 🔗 GitHub Action
• 💬 Report the issue on our Discord and help us improve

[chrjohn]

@jetbrains-junie

Please use the build-helper:uptodate-property the following way: use the FIX spec XML file to determine the base timestamp and only re-generate the classes if the JAR file in the specific quickfixj-messages-fix*/target folder either does not exist or is older than the XML spec file.

That should be good enough for our use case.

[jetbrains-junie[bot]]

Hey, it’s Junie by JetBrains! I started processing your request 🚀

[jetbrains-junie[bot]]

✅ Generation Status

• Code generation was successful

Message:

The build-helper:uptodate-property plugin was added to conditionally prevent rebuilding message classes. Maven profiles for each FIX version were created to execute code generation only if the respective spec files changed. Original code generation executions were removed from the main build section.

---

📌 Issues Detected During Processing

• Some issues occurred that may have limited the context available during generation.
• These did not prevent the operation, but fixing them could improve the results.

Message:

❌ I tried to build the project before getting started, but it didn’t work.

There might be issues with the environment or the code itself. Please check build log for more details.

More information:

• 🔗 GitHub Action
• 💬 Report the issue on our Discord and help us improve