On 21/01/16 13:19, Stian Thorgersen wrote:

util/embedded-ldap can we move this to testsuite?

It's used by both testsuite and examples ("ldap" and "kerberos" examples).

That was main motivation to move them to separate module, so examples are not dependent on testsuite.

Marek

On 21 January 2016 at 13:18, Stian Thorgersen <sthorger@redhat.com> wrote:

saml/saml-core I take it that's used by client and server? Should we just move saml-core to the root? Seems unnecessary to have a parent module with only one module inside.

On 21 January 2016 at 13:08, Stian Thorgersen <sthorger@redhat.com> wrote:

On 20 January 2016 at 23:27, Bill Burke <bburke@redhat.com> wrote:

"backends" (jpa, mongo, infinispan) were consolidated under
keycloak-model-(jpa, mongo, infinispan).

Integration module was moved around into:
adapters/
adapters/oidc
adapters/saml
spi/

connections, broker, social, events etc. were consolidated.

Modules I did not consolidate:

federation/*

I kept federation separate as I'm wondering what will happen with
kerberos and IBM JDK.  LDAP module depends on kerberos, so I kept that
separate too.

events/syslog

I'm deleting this. Shouldn't have been added in the first place as syslog can be done with the syslog appender for regular logging. Besides no one actually requested it.

 

Not sure if this is something we was removable or not as it depends on a
thirdparty library.

client-registration/*

Moved to integration. It's client lib for client registration service.

 

wildfly/*

Needs to stay as is. It's all specifics to WF and they can't be combined.

 

I don't know much about these modules so I kept them separate.
Stian/Marko can decide what they want to do here.

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

_______________________________________________
keycloak-dev mailing list
keycloak-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev