On 4/30/2014 11:52 AM, Marek Posolda wrote:
On 30.4.2014 16:14, Stian Thorgersen wrote:
>
> ----- Original Message -----
>> From: "Bill Burke" <bburke(a)redhat.com>
>> To: keycloak-dev(a)lists.jboss.org
>> Sent: Wednesday, 30 April, 2014 2:48:35 PM
>> Subject: Re: [keycloak-dev] isolate picketlink dependency please
>>
>> Primary Keycloak code should not depend on Picketlink. Picketlink
>> should always be hidden by SPIs. So, if we need to provide LDAP support
>> on EAP using an older version of Picketlink, then we write a separate
>> maven module using that older version of Picketlink and plug it in.
>>
>> Following me?
> Yep
>
>> Right now, it looks that only the Mongo data model has a PL dependency.
>> Correct?
> Yes (except authentication/authentication-picketlink of course)
Ok, I did not know that using picketlink is so big headache. Generally
said, it seems that if your project want to run on EAP, it's much easier
to depend on some 3rd party library, which can be bundled directly in
your WAR instead on "jboss" projects, which are available as modules in
EAP...:-(
It's not that. Its the whole brew, we-must-build-everything-we-ship,
way of doing things.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com