-
Notifications
You must be signed in to change notification settings - Fork 744
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
Spurious "SameNameButDifferent" warning on Lombok code with @Getter
and @Builder
#3187
Comments
What I see in the debugger before the warning is about to be emitted:
|
@Getter
@Getter
and @Builder
At the first point during tree traversal, where one of the offending entries ends up in the table:
It almost seems like So is this actually Lombok putting in the wrong start and end position for the symbol? Or is the warning coming out of the generated code, and Lombok's just pointing at the annotation which was used to generate it? Either way, it's doubly odd, because we have disabled warnings in generated code, and are still getting a warning from the generated code. |
Same here. You can also add
doesn't help. I also get a lot of VersionsLombok 1.18.24 |
For some Lombok code with a
@Getter
annotation, the "SameNameButDifferent" warning is triggered with an error message that seems to suggest it's treating the other types and annotations on the field as if they are field names. (?)Related to #2982, #3094, but different because it's now a spurious warning instead of an exception.
Versions in play:
Repro - NOTE: This repo was for reproducing a different issue, but it exhibits this issue also. You might want to comment out the MissingSummary line in
build.gradle.kts
, otherwise that causes an outright failure, but you should get the warning about SameNameButDifferent in the output regardless.The text was updated successfully, but these errors were encountered: