[keycloak-dev] [wildfly-dev] Using feature packs for custom distributions
mstrukel at redhat.com
Wed Jul 15 06:20:36 EDT 2015
Thanks Bob for confirming that skipping optionals should work.
My initial attempts at that were still pulling in the whole world, but I found it was due to a tiny bug in the tool I used that skipped some optionals but not all of them. Things look much more promising now ...
----- Original Message -----
> >> 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.
> This is what wildfly-swarm does.
> We consume the WF feature-packs, but only solve the tree from a few root
> module.xml’s to extract only the subset we need.
> And if it’s optional=“true”, we pretend we don’t need it. That helps a lot.
> Also, as soon as something pulls in weld, you’re pretty screwed, since weld
> then depends on most everything else, many times non-optionally.
> >> Another thing is provisioning of feature packs, which I address in another
> >> email.
> >> - marko
> >> _______________________________________________
> >> wildfly-dev mailing list
> >> wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
> >> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> >> <https://lists.jboss.org/mailman/listinfo/wildfly-dev>
> > --
> > Jason T. Greene
> > WildFly Lead / JBoss EAP Platform Architect
> > JBoss, a division of Red Hat
> > _______________________________________________
> > wildfly-dev mailing list
> > wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/wildfly-dev
> > <https://lists.jboss.org/mailman/listinfo/wildfly-dev>
More information about the keycloak-dev