You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (Jira)" <ji...@apache.org> on 2021/11/05 20:11:00 UTC

[jira] [Commented] (GROOVY-10346) why jackson has been chosen for yaml

    [ https://issues.apache.org/jira/browse/GROOVY-10346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17439470#comment-17439470 ] 

Paul King commented on GROOVY-10346:
------------------------------------

It supports YAML and TOML (Groovy 4). If you are not using either of those, you don't need it.

There is overlap with our json functionality but jackson had the built-in converters for YAML and TOML which we'd have to write and support.

If jackson supports pluggable json implementations we could swap out the jackson one for ours. It might be only 0.4M that we save if we still need the databind jar.

!image-2021-11-06-06-09-44-471.png!

> why jackson has been chosen for yaml 
> -------------------------------------
>
>                 Key: GROOVY-10346
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10346
>             Project: Groovy
>          Issue Type: Question
>            Reporter: Dmitry Lukyanov
>            Priority: Major
>         Attachments: image-2021-11-06-06-09-44-471.png
>
>
> if i understand everything correctly 2mb of jackson libraries imported into groovy only for
> YamlConverter class
> question: why this library that is large and duplicates groovy existing functionality like json ?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)