<div dir="ltr"><div>We have actually been talking about something kinda similar to this, but based on a redesign of the provisioning system rather than using layers.conf. The notes from the meeting we had about it are here:<br><br><a href="https://github.com/stuartwdouglas/wildfly-provisioning/blob/master/docs/src/main/asciidoc/design-doc.asciidoc">https://github.com/stuartwdouglas/wildfly-provisioning/blob/master/docs/src/main/asciidoc/design-doc.asciidoc</a><br><br></div><div>Basically it allows servers to be provisioned/patched in a manner kind of similar to what you describe.<br></div><div><br></div>Stuart<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 4, 2016 at 8:08 AM, Bill Burke <span dir="ltr"><<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I was thinking about how installation, patching, and distribution could<br>
be made easier and more flexible. What if layers.conf could reference a<br>
maven artifact?<br>
<br>
<br>
layers=org.keycloak:keycloak-modules:1.5<br>
<br>
The module layer of keycloak could be stored in a maven repo.<br>
Upgrading/patching could be just bump the version in layers.conf. If<br>
layers.conf also honored the list as a priority list, listed layers<br>
could override previously listed layers.<br>
<br>
If module layer the module defs also reference their jars as maven<br>
artifacts, patches are really small as they are just module.xml files.<br>
<br>
Bill<br>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote></div><br></div>