You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been successfully using jayway's json-path as a testing tool for our JSON output generation.
I'm now considering it as a runtime dependency, and the depending on json-smart (as said, an abandoned library, by its author admission) is standing out as negative.
I was not aware of JacksonJsonProvider, but it seems that due to #274 the json-smart dependency cannot be considered optional... pity.
I apologize I cannot offer development support to do eventual switches, just voicing another concern about the json-smart dependency, which you might want to consider when evaluating issues priorities.
…lso related to json-path#682, json-path#676, json-path#513, json-path#252)
* Replace hard-coded json-smart parser with one retrieved from context (where available) or default configuration.
* This enables a project to _exclude_ the transitive json-smart dependency when setting an alternative default configuration.
Hello,
First thanks for your great library and work on it.
Looking at refreshing our dependencies at JMeter, I noticed json-smart was kind of abandoned by its author.
So should'nt you switch to Jackson ?
By the way when do you plan a new release ?
Thank you and happy holidays.
Regards
The text was updated successfully, but these errors were encountered: