I think we were using the version of Jackson that was tied to the version
of Swagger we were using. In our pre-gradle build, we were pulling in
Jackson from directories for Swagger on gcm/where.
If we upgrade Jackson and Spring, then we should check our versions of
Swagger (do we have automated te
I just made a change to upgrade jackson and scala module to 2.8.2
On Thu, Sep 8, 2016 at 12:30 PM, Anthony Baker wrote:
> Speaking of jackson, anyone know why we’re not using v2.2.0 for the scala
> module? This is a dependency of geode-web-api.
>
> jackson.version = 2.2.0
> jackson-module-scala
Speaking of jackson, anyone know why we’re not using v2.2.0 for the scala
module? This is a dependency of geode-web-api.
jackson.version = 2.2.0
jackson-module-scala_2.10.version = 2.1.5
Anthony
> On Sep 8, 2016, at 10:32 AM, John Blum wrote:
>
> +1 to standardizing Geode on Jackson for JSO
+1 to standardizing Geode on Jackson for JSON processing.
+1 to using JsonPath/json-path-assert for testing interactions in Geode on
JSON docs.
On Thu, Sep 8, 2016 at 10:22 AM, Kirk Lund wrote:
> Yes, we should change all json parsing code to use jackson. However, we
> still need to write unit
Yes, we should change all json parsing code to use jackson. However, we
still need to write unit tests and that's what json-path-assert is for.
I've researched all of the ways to perform json assertions for unit tests
and test-path-assert is currently the best. It's from com.jayway same as
Awaitili
Can we get rid of TypedJson in favor of some standard json libraries?
On Thu, Sep 8, 2016 at 9:56 AM, Kirk Lund wrote:
> To support fixing up unit tests that involve json, I'd like to add in a
> dependency on com.jayway.jsonpath:json-path-assert.
>
> We already have a dependency on com.jayway.js
