Update OpenRewrite #2781 #2793
Closed
Update OpenRewrite #2781 #2793
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
Pankraz76
force-pushed
the
fix-rw-update
branch
from
b70df49 to
8f3cad9
Compare
Signed-off-by: Vincent Potucek <vpotucek@me.com>
Pankraz76
force-pushed
the
fix-rw-update
branch
from
8f3cad9 to
d1f7e2e
Compare
Pankraz76
commented
Dec 17, 2025
| - name: Gradle setup 🐘 | ||
| uses: gradle/actions/setup-gradle@v5 | ||
| - name: spotlessCheck | ||
| - name: Spotless ✨ |
Contributor
Author
There was a problem hiding this comment.
is this alignment of naming and convention something we want to consider, please?
| @@ -3,11 +3,6 @@ type: specs.openrewrite.org/v1beta/recipe | |||
| name: com.diffplug.spotless.openrewrite.SanityCheck | |||
| displayName: Apply all Java & Gradle best practices | |||
| description: Comprehensive code quality recipe combining modernization, security, and best practices. | |||
| tags: | |||
Contributor
Author
There was a problem hiding this comment.
just c&p from checkstyle approach. Imho this is not mandatory and kind of takes away the focus.
| @@ -64,5 +58,4 @@ recipeList: | |||
| - tech.picnic.errorprone.refasterrules.StreamRulesRecipes | |||
| - tech.picnic.errorprone.refasterrules.StringRulesRecipes | |||
| - tech.picnic.errorprone.refasterrules.TimeRulesRecipes | |||
| # - org.openrewrite.java.migrate.lang.FindVirtualThreadOpportunities # don't want to use: https://github.com/diffplug/spotless/pull/2684#discussion_r2433831887 | |||
Contributor
Author
There was a problem hiding this comment.
same here.
kind of takes away the focus.
| apply plugin: 'org.openrewrite.rewrite' | ||
| rewrite { | ||
| activeRecipe('com.diffplug.spotless.openrewrite.SanityCheck') | ||
| configFile = project.getRootProject().file("${rootDir}/gradle/rewrite.yml") |
Contributor
Author
There was a problem hiding this comment.
also follow project convent, thus move away from root not to bother around.
same here.
kind of takes away the focus.
Contributor
Author
|
needs java 21 as well: |
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.
Please DO NOT FORCE PUSH. Don't worry about messy history, it's easier to do code review if we can tell what happened after the review, and force pushing breaks that.
Please make sure that your PR allows edits from maintainers. Sometimes it's faster for us to just fix something than it is to describe how to fix it.
After creating the PR, please add a commit that adds a bullet-point under the
[Unreleased]section of CHANGES.md, plugin-gradle/CHANGES.md, and plugin-maven/CHANGES.md which includes:If your change only affects a build plugin, and not the lib, then you only need to update the
plugin-foo/CHANGES.mdfor that plugin.If your change affects lib in an end-user-visible way (fixing a bug, updating a version) then you need to update
CHANGES.mdfor both the lib and all build plugins. Users of a build plugin shouldn't have to refer to lib to see changes that affect them.This makes it easier for the maintainers to quickly release your changes :)