Re: [keycloak-dev] distribution of adapters

I also agree. I don't know deeply how adapters are designed, specially how much core is being used to avoid code duplication across different adapters. From what I saw, it seems that most of the code is provided by core which is a good smell. And only very specific code resides within each adapter, only the necessary bits to get the integration done. That said, I think most issues will be related with core than with a specific adapter. ----- Original Message ----- From: "Marek Posolda" <mposolda(a)redhat.com&gt; To: "Pedro Igor Silva" <psilva(a)redhat.com&gt;, "Bill Burke" <bburke(a)redhat.com&gt; Cc: keycloak-dev(a)lists.jboss.org Sent: Thursday, February 19, 2015 3:59:09 PM Subject: Re: [keycloak-dev] distribution of adapters I think I agree with Bolek that many separate adapter repos and releases is unecessary overhead. Especially if we're going to have even more adapter types than we have now... I can understand for non-maven non-java project, but why have separate adapter repo and releases for jetty, tomcat, eap etc? Only advantage is possibility to do separate release in case of adapter bug, but not sure if it would help much, because there is lot of common code in "core" and "adapter-core" . And: * in case of blocker bug in "core", you need to release whole keycloak anyway as this code is shared for both server and adapters * in case of blocker bug in "adapter-core", you need to release all java adapters anyway. Marek On 19.2.2015 18:28, Pedro Igor Silva wrote: