-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Groovy generated transform methods break parser #4254
Labels
Comments
Thanks for the detailed report and offer to help! We saw an issue with ToString reported before in Would you agree that's similar? Is there value in keeping both issues open? |
Issue reported on #4055 (comment):
Issue reported on this page:
Im sure that they are different issues. Stacktrace from the issue reported on this page is suggesting the error is coming from a different place.
|
3 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm seeing this on groovy class that uses groovy transform (
import groovy.transform.*
) such as @tostring, @EqualsAndHashCode.What version of OpenRewrite are you using?
I am using https://github.com/gtiwari333/openrewrite-groovy-bug/blob/main/init.gradle
How are you running OpenRewrite?
%./gradlew clean rewriteRun --init-script init.gradle --info
What is the smallest, simplest way to reproduce the problem?
Checkout the following project and run
./gradlew clean rewriteRun --init-script init.gradle --info
Im seeing similar behavior with both jdk17 and jdk21
https://github.com/gtiwari333/openrewrite-groovy-bug/blob/main/README.md
What did you expect to see?
No failures. AutoFormat recipe should run on the code.
What did you see instead?
What is the full stack trace of any errors you encountered?
Run the
./gradlew clean rewriteRun --init-script init.gradle --info
command to get full stacktrace. I've provided relevant bits above.Are you interested in contributing a fix to OpenRewrite?
Not too familiar how AST works. But i can try.
The text was updated successfully, but these errors were encountered: