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 think you may be aware of this, but I wanted to let you know of an issue I ran into while upgrading from 2.0.5 to 2.0.6 within my Dropwizard 0.9.2 application. Dropwizard 0.9.2 currently depends on Jackson 2.6.3 (and will be upgrading to Jackson 2.7.4 in Dropwizard 1.0.0).
As part of the Riak client 2.0.6 version, #615 upgraded Jackson to 2.7.3 which changed the method signature of checkAndFixAccess in jackson-databind, which resulted in a lot of these errors being thrown within my application (since I was creating a shaded-jar with Jackson 2.6.3 from Dropwizard taking precedence over Jackson 2.7.3 in the Riak client):
Just pointing this out in case anyone else runs into this. For the time being, I'm going to stick with the 2.0.5 Riak client when using Dropwizard 0.9.2 instead of messing around with my shaded jar settings.
I think you may be aware of this, but I wanted to let you know of an issue I ran into while upgrading from 2.0.5 to 2.0.6 within my Dropwizard 0.9.2 application. Dropwizard 0.9.2 currently depends on Jackson 2.6.3 (and will be upgrading to Jackson 2.7.4 in Dropwizard 1.0.0).
As part of the Riak client 2.0.6 version, #615 upgraded Jackson to 2.7.3 which changed the method signature of
checkAndFixAccessinjackson-databind, which resulted in a lot of these errors being thrown within my application (since I was creating a shaded-jar with Jackson 2.6.3 from Dropwizard taking precedence over Jackson 2.7.3 in the Riak client):Just pointing this out in case anyone else runs into this. For the time being, I'm going to stick with the 2.0.5 Riak client when using Dropwizard 0.9.2 instead of messing around with my shaded jar settings.