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
#1821 nullpointer due to @BeanMapping via inheritance #1822
Conversation
still an issue.. I know that @Captain1653 also looked at it.. Just need to find some time to think about this one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where exactly was the NPE before? There are a lot of changes to be able to determine what fixes the problem.
Do we really need a builder for the BeanMapping
, why can't we keep the old methods? Looking at the builder it seems that it is the same as the methods before.
processor/src/main/java/org/mapstruct/ap/internal/model/source/BeanMapping.java
Show resolved
Hide resolved
Yes.. but isn't that always the case..? For me I start to use builder when the number of constructor args starts to approach 10 args. Slowly we are moving all our classes to builders, so its unclear to me why we would apply that here. btw: I added the mirror as constructor arg. |
The problem was caused because we inherited the I probably should have split stuff in different commits. |
We are passing the utils all over the place. Perhaps we should just pass the One think which is now not clear to me. If before we had an NPE, why isn't some test failing due to reporting? |
I added a failing test :). |
Yes that test confused me. I thought that it was failing when we were reporting something. Anyways LGTM, feel free to merge |
…ruct#1822) (cherry picked from commit ade4f4d)
mapExtended
does not have the@BeanMapping
, but still it tries to resolve the prism.SelectionParameters
for inheritance too and leaving out theresultType
.BeanMapping
.BeanMappingMethod
, but useBeanMapping