-
-
Notifications
You must be signed in to change notification settings - Fork 143
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
Jackson 2.8.11
release for Scala module
#359
Comments
hmm.. This one also fails with the same error as #357 Is it something wrong with my machine? .... We need to figure this out.. |
Hmmh. It could be one of backported fixes. While nothing looks particularly suspicious, it could be either one of:
One thing you could try locally is to build against |
I have not tracked the issue down yet, but this is what I've found out so far: I've been using the 2.8-branch for testing - I guess there are less changes between 2.8.10 and 2.8.11. The problem is this line: Line 29 in fd3055b
In 2.8.10, _mapDeser ends up with SortedMapDeserializer I have not figured out why yet, but I write it here for info/starting point |
Ok. I don't know if change is problematic (it may well be), but for context that "untyped" deserializer is for use with |
I found it the change causing the problem: FasterXML/jackson-databind@4675896#diff-71da9745111f01bc93519d574c2f9fabL416 if (baseType.isInterface()) {
// The scala-test was relying on this line.
newType = baseType.refine(subclass, tb, null, new JavaType[] { baseType });
} else {
newType = baseType.refine(subclass, tb, baseType, NO_TYPES);
} For 2.8.10, we end up with isMapLike == true, but for 2.8.11 we end up with isCollectionLike == true which breaks down the line.. I'm not sure if I have found a regression or not.. What do you think? |
Hmmh. This could also be related to the fact that Scala module is not necessarily supporting type refinement (to support collection- / map-like) in the right place: things have changed a little. New code in this specific place is, I think, (more) correct. But I don't quite understand negative ramifications on Scala side. Getting |
2.8.11 released |
I hope this should be easier than 2.9. So, 2.8.11 is out:
https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.8.11
and it'd be good to get Scala module out too. This is planned to be the last full 2.8.x release, closing the branch. So should perhaps simplify things a bit (I forget if there's any scala version deprecation involved here, perhaps not).
The text was updated successfully, but these errors were encountered: