[keycloak-dev] [wildfly-dev] Using feature packs for custom distributions

Stian Thorgersen stian at redhat.com
Mon Jul 13 09:13:39 EDT 2015

As I see it the main issue with using core or servlets is the fact that we have to redefine modules.

Currently AFAIK when pulling in a feature pack you end up pulling in all modules for that feature pack even if you disable subsystems/extensions that rely on those modules. Would it not be better to have individual subsystems define what modules they require and only pull in the required modules for the enabled subsystems/extensions? That would allow us to build on WF full and get all module definitions from there, while still reducing the size of our distribution.

----- Original Message -----
> From: "Tomaž Cerar" <tomaz.cerar at gmail.com>
> To: "Jason Greene" <jason.greene at redhat.com>
> Cc: wildfly-dev at lists.jboss.org, "keycloak dev" <keycloak-dev at lists.jboss.org>
> Sent: Monday, 13 July, 2015 2:53:26 PM
> Subject: Re: [wildfly-dev] Using feature packs for custom distributions
> On Thu, Jul 9, 2015 at 5:13 PM, Jason Greene < jason.greene at redhat.com >
> wrote:
> > For our use-case this would also be addressed by wildfly providing a
> > feature-pack definition that’s somewhere between servlet-feature-pack and
> > full-feature-pack - as long as it contains datasources support, and jaxrs
> > support …
> I think this is a good idea, to skip optional deps.
> Should we add another feature pack "wildfly-web" that would be near EE web
> profile?
> We could only have feature pack without corresponding distribution.
> This would allow downstream projects like keycloak to easier build custom
> distribution using such feature pack.
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

More information about the keycloak-dev mailing list