You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading Language Support for Java(TM) to version 1.36, visual studio code started failing to generate MapStruct Mappers with the following error :
Error occured while building workspace. Details:
message: No implementation was created for xxxMapper due to having a problem in the erroneous element java.util.ArrayList. Hint: this often means that some other annotation processor was supposed to process the erroneous element. You can also enable MapStruct verbose mode by setting -Amapstruct.verbose=true as a compilation argument.
I'm using Maven with Lombok 1.18.30 and MapStruct 1.5.5.Final. Command line compilation works just fine, the issue arises only when building using the VS Code IDE.
Rolling back Language Support for Java(TM) plugin in VS Code to version 1.35.1 solves the issue.
Below is my maven annotationProcessorPaths configuration. I can try and provide a basic application to reproduce the issue, if it helps.
This is a duplicate of #3836 . #3833 just updated the name of the file to better reflect what it is. We've been running off the latest Lombok for some time now.
el problema esta en que las librerias de lombok del editor con respecto al proyecto son diferentes
para el caso de vscode se debe cambiar la version del lombok por la de tu proyecto en la siguiente ruta
Hi,
After upgrading Language Support for Java(TM) to version 1.36, visual studio code started failing to generate MapStruct Mappers with the following error :
I'm using Maven with Lombok 1.18.30 and MapStruct 1.5.5.Final. Command line compilation works just fine, the issue arises only when building using the VS Code IDE.
Rolling back Language Support for Java(TM) plugin in VS Code to version 1.35.1 solves the issue.
Below is my maven annotationProcessorPaths configuration. I can try and provide a basic application to reproduce the issue, if it helps.
Best regards,
Nicolas
The text was updated successfully, but these errors were encountered: