-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[BUG] UI Error when a generated Field is used on annotation #3529
Comments
Does using a fully qualified name fix the problem? For example: |
Hi @rspilker ! Also with full qualified name the problem exists :-( thanks for your help ! |
Can reproduce this in eclipse, two files are required. I have already found out that at some point the initializer of the generated field gets replaced with |
@Rawi01 do you have some plan how to fix it ? |
Yes, I have almost finished my patch for this problem |
@Rawi01 that sounds great ! I would also test your patch if you like. |
Eclipse copies the field initializer source code if it is a constant. For generated nodes we have to read it from the ast node and not from the source file.
Eclipse copies the field initializer source code if it is a constant. For generated nodes we have to read it from the ast node and not from the source file.
@Rawi01 do you know when this fix will be available ? Thanks ! |
@Rawi01 any news here ? It would be great if we could have some fix for it .. thanks lot ! |
Eclipse copies the field initializer source code if it is a constant. For generated nodes we have to read it from the ast node and not from the source file.
Oh, I forgot to create a pull request for the changes, sorry. |
@Rawi01 thank you for the fix ! How often will the Snapshot be build so that i can try it ? |
@rzwitserloot the edge-release page says always |
This is part of the latest edge release, all feedback is welcome. |
Now It's even worse to me, everytime I change a java class file the errors for the constants comes back Only workaround I found is everytime i change a class file to delete all error messages, maven package, and refresh. I'll go back to lombok 31 subversion which was only throwing this errors from time to time |
@getzabelz i see no more problems .. that's interesting that you have now more problems .. |
Maybe I have something wrong in my local? Tried with a fresh installed Eclipse and I still get the same, actual config is:
An example usage that throws error: throws following error marker: Only workaround that temporarily works for me is removing all markers, maven package and refresh and still It only works half of the times... any idea? |
@getzabelz Can you share a full example and also check if there is an error in your eclipse error log? |
Checked eclipse logs and I don't see anything related to Lombok. I've been doing tests in a fresh setup and It seems that It breaks whenever I use QueryDSL with Lombok and @FieldNameConstants, could it be a conflict in between processors? I can't find any information or workaround, anyone got any clue? My pom.xml configuration related to both in case It's useful:
|
Describe the bug
We are using lombok 1.18.30 within eclipse 2023-09.
We use the @FieldNameConstants Annotation a InnerClass with static final Fields will be generated.
If we use the static final Fields on a annotation there is no Compile Error but we see a Error on the Classs itself
To Reproduce
The Problems View is empty, and the code works if you run it ...
You will find a sample eclipse project here
Sample-Project.zip
I have also created a issue in jdt-ui eclipse-jdt/eclipse.jdt.ui#865 but a project member thought it is maybe a problem of lombok.
Thanks for any help.
The text was updated successfully, but these errors were encountered: