[keycloak-dev] Support both Jackson and Jackson 2

[Stian Thorgersen]

----- Original Message -----
> From: "Bill Burke" <bburke at redhat.com>
> To: "Stian Thorgersen" <stian at redhat.com>
> Cc: keycloak-dev at lists.jboss.org
> Sent: Monday, 3 November, 2014 4:44:12 PM
> Subject: Re: [keycloak-dev] Support both Jackson and Jackson 2
> 
> 
> 
> On 11/3/2014 10:43 AM, Stian Thorgersen wrote:
> >
> >
> > ----- Original Message -----
> >> From: "Bill Burke" <bburke at redhat.com>
> >> To: "Stian Thorgersen" <stian at redhat.com>
> >> Cc: keycloak-dev at lists.jboss.org
> >> Sent: Monday, 3 November, 2014 4:26:58 PM
> >> Subject: Re: [keycloak-dev] Support both Jackson and Jackson 2
> >>
> >>
> >>
> >> On 11/3/2014 10:23 AM, Stian Thorgersen wrote:
> >>>
> >>> ----- Original Message -----
> >>>> From: "Bill Burke" <bburke at redhat.com>
> >>>> To: keycloak-dev at lists.jboss.org
> >>>> Sent: Monday, 3 November, 2014 4:15:17 PM
> >>>> Subject: Re: [keycloak-dev] Support both Jackson and Jackson 2
> >>>>
> >>>> Why is 811 a problem?  We can just ship jackson 1.9.x
> >>>
> >>> What about folks that use Jackson 2 in their applications and want to use
> >>> our adapter?
> >>>
> >>
> >> Shouldn't be a problem.  Different 1.9.x/2.x are different packages and
> >> our adapter doesn't use JAX-RS provider.  So there should be no clashes.
> >
> > True, so actually 811 is only a problem for admin client java api as it's
> > using ResteasyClientBuilder. I guess we can quite easily make sure that
> > always uses Jackson provider?
> >
> > As Jackson is becoming old, would it make sense that we swap to Jackson2?
> > Or would it not be possible to do that on AS7/EAP6?
> >
> 
> Not a technical problem at all, but you know how our productization is.

Oh, crap forgot about that ;)

I'll just make sure the admin client uses Jackson then.

> 
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
>