[keycloak-dev] public/private api module structure

[Bill Burke]

On 8/13/2015 1:47 AM, Stian Thorgersen wrote:
>>> For users if they included a single module/jar with the apis for all SPIs
>>> they would then have to figure out what belongs to what. That's where I
>>> think it's cleaner to split it up.
>>>
>>
>> This is an honest question.  Why do they have to figure out what belongs
>> to what?  And why do they care?  They will be looking at documentation
>> and javadocs.
>
> There's two types of devs those that reads docs and javadocs and does that don't. Personally I'm a bit of both I refer to javadocs sometimes, but quite frequently I look through the source code and that's much simpler if it's modularized. However, I've thought about it a bit and I think we can achieve the same modularity with packages and by making sure "keycloak-server-api" mainly contains interfaces.
>

Interfaces and simple helper or abstract classes.


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