[wildfly-dev] Feature pack provisioning

Brian Stansberry brian.stansberry at redhat.com
Mon May 2 12:39:34 EDT 2016

On 5/2/16 9:35 AM, Juraci Paixão Kröhling wrote:
> On 16.07.2015 00:11, Jason Greene wrote:
>> As to #3, the notion of a runtime provisioning system similar to something like a yum tool is a long term goal, which I totally agree we need, but its going to be a while before we can get there (Definitely not 10 nor 11). Alexey has been assembling requirements for it, and has some ideas around the packaging format. We really want to get it right, so the plan is to let it grow organically until its proven to be a solid system, and only then switch to it.
>>> On Jul 9, 2015, at 9:02 AM, Marko Strukelj <mstrukel at redhat.com> wrote:
>>> 3) provision into existing Wildfly server detecting version mismatches, and configuring existing and additional subsystems for Keycloak to run properly.
> Is there any up-to-date information about this feature, such as plans,
> roadmap, branches with PoC for testing, ...?
> While the document on [1] is very useful in outlining the idea, I
> couldn't find out if there's any branch I could use for testing or if
> it's already being planned for a specific WF release.
> Similar to Keycloak, Hawkular might benefit from a feature like this.
> 1 -
> https://developer.jboss.org/wiki/LayeredDistributionsAndModulePathOrganization

I'll defer to Alexey to respond re: current status, but I just wanted to 
point out that wiki page is not really a design doc for this. That 
describes how layering currently works, since EAP 6.2.

Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat

More information about the wildfly-dev mailing list