Filip Hrisafov

Thanks a lot @cowtowncoder for the detailed post. >First things first: behavior of Jackson 3 is not really expected to be same as that of Jackson 2.x: a big reason...

>CollectionMappingStrategy does not seem to apply there ? Maybe there should be another configuration option for handling the cleaning of target properties, so that it would be possible to clear...

>Oh I missed that, but I think it still does not suit for my use case, as setting the collection will effectively replace all its elements (thus tiggering delete statements...

>Do you have an input on how this CollectionMappingStrategy option should behave ? Refering to https://mapstruct.org/documentation/stable/reference/html/#collection-mapping-strategies. You are talking about the new `CollectionMappingStrategy` for using `retainAll`? That can indeed a...

Thanks for the analysis @maxifridge, I believe that you are on the right track. Reading up on what you wrote I think that the second option would make more sense....

@jijoraju can you please clarify what you exactly mean? The title of the issue doesn't sound really related to what you have described in the issue. Can you also please...

Looking at your provided example @jijoraju this is something that we do not want to support. You should do what @jakubbadecki proposed

@mipo256 you know that you can do ```java interface CommonMapping { static Instant getInstant() { return Instant.now(); } } ``` and then ``` @Mapper(imports = {CommonMapping.class}) interface SpecificInterface2 { @Mapping(target...

I've had a bit more thought about this one. Something similar was also asked about from @marceloverdijk in #3846. I'll reopen this so that perhaps we can add something like...

>Just adding my two cents, we're also using something like `now()` quite often, so something like this would come quite handy. I have not been a fan of this, but...