Versioning strategies in Junit support. #274
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
…ort. If the user wishes to iterate across sources/targets instead of releases for the JUnit annotations, there is now an attribute that can be overridden to support that.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Implement ability to change default versioning strategy in JUnit support.
If the user wishes to iterate across sources/targets instead of releases for the JUnit annotations, there is now an attribute that can be overridden to support that.
This is a breaking change in the JUnit API, but since this is not yet a fully stable release,
I am leaving the versioning as-is for this change. This only affects custom compiler
implementations with custom JUnit parameters anyway. For 99.99% of use cases, this will not
affect anything.