[build] Fix for #4555: reintroduce Maven testing. #4565
Merged
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
With no arguments, the script tests every grammar that contains a pom.xml.
The best way I know is to just do a 'mvn clean' at the root.
Member
|
@kaby76 thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Please merge #4570 first.
This is a fix for #4555. With this PR, the Maven tester is once again checked. While it misses many features that the trgen tester does, the Maven tester still is a good, quick check, and people seem to prefer that.
This PR changes:
mvn cleanis done at the root for a quick sanity check of the root pom.xml.Some of the grammars had problems in their pom.xml: bison, clif, ocl, pike, ruleworks, spl, teal, tinyos_nesc. These were corrected in various ways.