Version withour json-smart

[nikolakoco89]

Hello,

I would like to try my luck, with a new post. Are you planning a version without json-smart? Since the library is abandoned by it's user, one of it's dependencies is really outdated and is causing conflicts in my project.

[Alanscut]

agree, I think Jackson would be more appropriate.

[LaurentT]

Hello,
same as @nikolakoco89 , this way one could completely exclude json-smart dependency from pom.
and then we could also think making 'net.minidev.json.*;resolution:=optional' in the build gradle so we are able to choose the Jackson implementation of JsonProvider and MappingProvider?

[jobmission]

+1

[nikolakoco89]

Hi everyone,
due to unresponsiveness regarding this manner, I've switched to using JSON Pointer.

Cheers

[amergey]

Hello,
same as @nikolakoco89 , this way one could completely exclude json-smart dependency from pom.
and then we could also think making 'net.minidev.json.*;resolution:=optional' in the build gradle so we are able to choose the Jackson implementation of JsonProvider and MappingProvider?

+1 for this solution, it would make easier to use json-path without forcing to depends of json-smart which seems dead and even worst can lead to the jvm to be killed with jdk11 (see https://bitbucket.org/connect2id/nimbus-jose-jwt/issues/239/switch-to-other-json-library for example)

[jxv120]

Hello guys,
Not only json-smart is abandoned but it have a critical vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2021-27568.

[uschindler]

Please help to get rid of this library. It looks like it is only hardcoded at some places (for no reason).