As some of you may know, support for Scala 2.10 is finally being dropped from Scala module, for Jackson 2.12:
https://github.com/FasterXML/jackson-module-scala/issues/480 One practical question, then, is what to do regarding the version management section of `jackson-bom`, for `jackson-module-scala_2.10`. Leaving entry as is would lead to a dangling reference, referencing non-existing 2.12.0 version, which seems wrong. Two obvious choices would be: 1. Drop the entry altogether, define no version 2. Define latest available version (2.11.3 currently) I am not quite sure which I prefer: I might go with (2) if it was any other module -- since use of previous minor version generally works for "leaf" modules (ones that depend on core, but that nothing else depends on) -- but would probably not work very well for Scala module as it uses strict check to ensure that core module versions used have same minor version as Scala module. So databind 2.12.0 and Scala module 2.11.x would fail on registration of Scala module. So I guess I am leaning towards (1), removing the version management entry. Any thoughts on this? -+ Tatu +- -- You received this message because you are subscribed to the Google Groups "jackson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-dev/CAL4a10ghx%3D8-4LS-p8k-skBojNOGQpy7XM9Es6S2pM2C8imJTg%40mail.gmail.com.
