[jira] [Created] (GROOVY-12433) Move groovy-yaml, groovy-toml and groovy-csv to Jackson 3

["Scott Murphy Heiberg (Jira)" <ji...@apache.org>]

Scott Murphy Heiberg created GROOVY-12433:
---------------------------------------------

             Summary: Move groovy-yaml, groovy-toml and groovy-csv to Jackson 3
                 Key: GROOVY-12433
                 URL: https://issues.apache.org/jira/browse/GROOVY-12433
             Project: Groovy
          Issue Type: Improvement
          Components: groovy-yaml, XML Processing, groovy-csv, groovy-toml
            Reporter: Scott Murphy Heiberg
             Fix For: 7.0.0-alpha-1


groovy-yaml, groovy-toml and groovy-csv are built on Jackson 2 ({{com.fasterxml.jackson}} 2.22.x). Spring Boot 4 uses Jackson 3 ({{tools.jackson}}) by default, so an application on Spring Boot 4 that uses one of these modules carries both major versions and has to manage the Jackson 2 one itself. Jackson 2 and 3 use different packages and coordinates, so having Jackson 3 on the classpath does nothing for these modules.

None of the three modules exposes a Jackson type in its public API, so they can move to Jackson 3 without source changes for callers.

Proposal:
* Depend on {{tools.jackson}} 3.1.6, the version Spring Boot 4.2 manages. {{jackson-datatype-jsr310}} is no longer needed; java.time support is built into Jackson 3 databind.
* Build every mapper with {{configureForJackson2()}} so behaviour is unchanged: properties in declaration order, unknown properties rejected, nulls for primitives and trailing tokens accepted. The CSV mapper also keeps {{SORT_PROPERTIES_ALPHABETICALLY}}, which Jackson 2's {{CsvMapper}} enabled itself and the user guide documents.
* {{XmlParser.parseAs}} and {{parseTextAs}} load jackson-databind reflectively; use Jackson 3 when present and fall back to Jackson 2.
* Jackson 3's YAML backend uses SnakeYAML Engine rather than SnakeYAML, so the SnakeYAML alias recipe from GROOVY-12358 needs {{org.yaml:snakeyaml}} declared explicitly, as the user guide already anticipates.

Jackson 3 still uses {{com.fasterxml.jackson.annotation}}, so {{@JsonProperty}}, {{@JsonFormat}} and the other annotations in user code keep working.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)