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
Thanks for the nice words. We are glad that you like MapStruct 😄 .
The problem is that you have only mapstruct-processor in the annotationProcessorPaths and only that dependency is passed to the javac compiler.
The annotationProcessorPaths is there only since 3.5 so it is really strange how the mapstruct processor is invoked. In any case in order to make it work correctly you have 2 options:
Add the lombok dependency to the annotationProcessorPaths as well. Then it will be picked up by the compiler and it should work.
Ad the mapstruct-processor jar to your pom as a provided dependency. You will have to remove the annotationProcessorPaths in that case and the compiler will pick up the processors from your dependency. The reason why we are suggesting to use the annotationProcessorPaths is because by doing that you won't be able to use something from the mapstruct-processor module by accident. An additional reason to put it in the pom dependencies is this issue from IntelliJ (in case you are using InteliiJ 😄
You can also have a look at the mapstruct-lombok example from our repository.
I am going to close this issue as it is a problem in the configuration 😄
mapstruct/mapstruct#1270 (comment)
Thanks for the nice words. We are glad that you like MapStruct 😄 .
The problem is that you have only
mapstruct-processor
in theannotationProcessorPaths
and only that dependency is passed to the javac compiler.The
annotationProcessorPaths
is there only since3.5
so it is really strange how the mapstruct processor is invoked. In any case in order to make it work correctly you have 2 options:Add the lombok dependency to the
annotationProcessorPaths
as well. Then it will be picked up by the compiler and it should work.Ad the
mapstruct-processor
jar to your pom as a provided dependency. You will have to remove theannotationProcessorPaths
in that case and the compiler will pick up the processors from your dependency. The reason why we are suggesting to use theannotationProcessorPaths
is because by doing that you won't be able to use something from themapstruct-processor
module by accident. An additional reason to put it in the pom dependencies is this issue from IntelliJ (in case you are using InteliiJ 😄You can also have a look at the mapstruct-lombok example from our repository.
I am going to close this issue as it is a problem in the configuration 😄
Originally posted by @filiphr in mapstruct/mapstruct#1270 (comment)
The text was updated successfully, but these errors were encountered: