Draft
Make full-fix-latest the default build profile; restrict minimal-fix-latest to CodeQL#1279
Conversation
…ix-latest for CodeQL only
Copilot
AI
changed the title
chore: make full-fix-latest the default build profile, keep minimal-fix-latest for CodeQL only
Make full-fix-latest the default build profile; restrict minimal-fix-latest to CodeQL
Jul 17, 2026
Copilot created this pull request from a session on behalf of
chrjohn
July 17, 2026 13:40
View session
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously
minimal-fix-latestwasactiveByDefault, so every build — including developer and regular CI builds — used a stripped-down subset of the FIX Latest Orchestra spec.full-fix-latesthad to be explicitly activated to build the complete spec.This inverts the default:
full-fix-latestis nowactiveByDefault;minimal-fix-latestremains available but is only activated explicitly by the CodeQL workflow (which needs it to stay within heap limits). Maven'sactiveByDefaultsemantics mean that explicitly passing-Pminimal-fix-latestautomatically deactivatesfull-fix-latest— no CodeQL workflow changes required.Profile changes
quickfixj-messages-all/pom.xml: swapactiveByDefaultfromminimal-fix-latest→full-fix-latest; update comment onminimal-fix-latestto CodeQL-onlyquickfixj-messages-fixlatest/pom.xml: addactiveByDefault=truetofull-fix-latest(Javadoc skip active by default for this large module)CI
maven.yml: dropminimal-fix-latestfrom both Linux/macOS and Windowsrun:commands — full spec now built by defaultcodeql-analysis.yml: unchanged; continues to activate-Pminimal-fix-latestexplicitlyDocumentation
README.md,quickfixj-messages/readme.md,quickfixj-stress-test/README.md,AGENTS.md: removeminimal-fix-latestfrom user-facing build commands; update profile descriptions to reflect new defaults