[keycloak-dev] public/private api module structure

[Bill Burke]

On 8/13/2015 9:07 AM, Stian Thorgersen wrote:
> I'm happy with:
>
> keycloak-core-api
> keycloak-client-api
> keycloak-server-api
>
> With regards to the protocol specific parts are you thinking those would be client specific things for each protocol? For example JWT utils?

Everything.  For example, I have a helper abstract base class for 
Authenticator and RequireActionProvider.  Mappers can get access to the 
SAML Document model.



>
> Further I think we should put core provider implementations into keycloak-services or maybe keycloak-default-providers or something. Then only have separate modules for those providers that need to be pluggable (jpa, mongo, etc..).
>
> Not sure if the way I counted it is accurate, but we seem to have 200 maven modules!!
>

Yeah, its insane...Its pretty much why I punted on converting from a WAR 
to modules :)

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