Upgrade gradle to 8.2.1 and fix some warnings #92
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
nvervelle
force-pushed
the
upgrade-gradle-to-8.2.1
branch
from
f4a2379
to
9483751
Compare
|
Hi @nvervelle! And thanks a lot for this contribution. It's vacation time for a lot of us, but I too am hoping this is maintained and will get merged into a new release 🙂 |
|
Hi @nvervelle ! Thanks for upgrading gradle version. The project is still maintained although not much work is currently going on. Feel free to work on #41 . |
radrys
approved these changes
Jul 17, 2023
This was referenced Jul 18, 2023
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.
Hi !
Is the project still maintained ? Just want to know if I should send PR here or work on my own fork.
This is just an upgrade of gradle to the current version (allowing Java 17 for example) and fix of a few warnings issued by IntelliJ when committing the files.
I'm also interested in working on #41 , that is being able to use opa in docker for the plugin instead of locally installed opa. Tell me if you would be interested also