Skip to content

Could GSON be optional? / Jackson support?Β #2961

@sebdehne

Description

@sebdehne

I really appreciate the good work which has good into this excellent library, but does Jedis really need GSON for JSON-support?

For example there is a security issue with GSON (google/gson#1991) which now becomes everybodies problem who uses Jedis.
Would it be possible to at least make GSON optional such that Jedis still works even without GSON on the classpath? Or support both Jackson and GSON (which ever is found on the classpath) if one really needs the JSON capabilities?

Thanks a lot. If you need help - I can submit a change which makes gson optional.

Metadata

Metadata

Assignees

No one assigned

    Labels

    breakingchangePull request that has breaking changes. Must include the breaking behavior in release notes.dependenciesPull request that updates a dependency

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions