Skip to content
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

Don't re-use dynamic serializers for property-updating copy constructors #2181

Closed
wants to merge 1 commit into from

Conversation

morj
Copy link

@morj morj commented Nov 7, 2018

Reason: dynamic serializers may hold property name and therefore must be re-created when the property changes.
(backport of 3b1cf096779bf3756794d2e325088b73b9e66e1b from 3.0 branch)

Feel free to re-create this change yourself it you accept it, but signing the CLA can take a while. Our prioirty is to have it in central with upcoming 2.10+ releases.

reason: dynamic serializers may hold property name and therefore
must be re-created when the property changes
(backport of 3b1cf09 from 3.0 branch)
@cowtowncoder
Copy link
Member

Thank you for submitting this! I'll have to think this through once more but I think you are right.
And if so, I think I may want to manually merge it in for 2.9 as well.

@morj
Copy link
Author

morj commented Nov 8, 2018

2.9.7+ will be great as well! Thank you!

@morj
Copy link
Author

morj commented Nov 21, 2018

@cowtowncoder can you please give a status update on this?

@cowtowncoder cowtowncoder added this to the 2.9.8 milestone Nov 23, 2018
@cowtowncoder
Copy link
Member

@morj sorry, I have not had much time for Jackson for past 2 weeks, but I am now merging this. Thank you again for help here! It will go in 2.9.8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants