Re: [keycloak-dev] public/private api module structure
On 13.8.2015 15:22, Bill Burke wrote:
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 :)
It looks to me that for the server, we have "just" around 50-60 modules
:-)
Many maven modules are needed for adapters and their tests (For example
there is jetty-core, jetty8, jetty91, jetty92 and each of them also has
separate testsuite module etc) . Not sure how we can improve on it, but
looks to me that not much as each app-server version we want to support
needs separate adapter with the classes related to that version. There
are also quite many maven modules for examples.
Marek