Compiler errors, after Implementation is generated #3904
Replies: 1 comment 4 replies
-
|
Hi @trico-tillster! Wow, that's a nasty bug. I created an issue for this: The only workaround I know is cumbersone: Try to isolate all your code regarding the class Something like: public class WorkaroundMapper {
OverrideDto myCustomMapping(Override override) {
// custom mapping
return null;
}
}
@Mapper(uses = WorkaroundMapper.class)
public class YourMapStructMapper {
// ....
} |
Beta Was this translation helpful? Give feedback.
-
|
@trico-tillster you can also try adding |
Beta Was this translation helpful? Give feedback.
-
|
@filiphr I've given a try with this approach, still generated code discards the import java.lang.Override. |
Beta Was this translation helpful? Give feedback.
-
|
@thunderhook many thanks on paying attention to this, creating a ticket and and providing a solution. |
Beta Was this translation helpful? Give feedback.
-
|
Of course, just provided a temporary solution if you cannot wait for a fix. 🙂 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've 1 object to be mapped to another, if one of them contains a object called Override compiler fails.
This happens because generated code adds the
@Overrideannotation to the implementation method, and compiler gets confused with the import class.I've tried to search for a config to manipulate the generated annotation, something like updating it to @java.lang.Override, but I was not able.
I'm also not able to change the model Override class name to other, because this is a generated code from an external json schema.
Thought it would be helpful to mention this here.
Any clues how to solve this?
Beta Was this translation helpful? Give feedback.
All reactions