#106 Fix: could not compile in Gradle #112
Open
Conversation
This file contains 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
added 2 commits
June 5, 2023 14:57
- curly bracket missing from plugins - gradle plugin version was not found -> updated
- Using junit-vintage-engine to make test run
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.
Summary of this PR
a. missing curly bracket in build gradle
b. serenity gradle plugin version was not found.
Intended effect
It will build with Gradle again. Tests will run again with Gradle.
How should this be manually tested?
Just build the project first:
gradle clean build -x testThen run the tests:
gradle clean testSide effects
N/A
Documentation
N/A
Relevant tickets
#106
#105
Screenshots (if appropriate)
N/A