Execute Grammar-Kit Tasks Before Build #372
Open
Conversation
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.
To avoid forgetting to regenerate custom language source code after editing .flex or .bnf files—or when switching branches—this update adds a build dependency to ensure Grammar-Kit tasks are executed before compilation or build.
Implementation Summary
Add a task dependency so that Grammar-Kit runs automatically before compileJava or build-related tasks.
Ensures the latest lexer/parser classes are always generated based on the current grammar definitions.
Benefits
Prevents build failures or runtime errors due to stale generated code
Improves reliability when switching between branches with different grammar definitions
Reduces manual regeneration steps for developers