[wildfly-dev] enhancement: layers.conf can use maven artifacts

[Stuart Douglas]

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:

https://github.com/stuartwdouglas/wildfly-provisioning/blob/master/docs/src/main/asciidoc/design-doc.asciidoc

Basically it allows servers to be provisioned/patched in a manner kind of
similar to what you describe.

Stuart

On Thu, Aug 4, 2016 at 8:08 AM, Bill Burke <bburke at redhat.com> wrote:

> I was thinking about how installation, patching, and distribution could
> be made easier and more flexible.  What if layers.conf could reference a
> maven artifact?
>
>
> layers=org.keycloak:keycloak-modules:1.5
>
> The module layer of keycloak could be stored in a maven repo.
> Upgrading/patching could be just bump the version in layers.conf. If
> layers.conf also honored the list as a priority list, listed layers
> could override previously listed layers.
>
> If module layer the module defs also reference their jars as maven
> artifacts, patches are really small as they are just module.xml files.
>
> Bill
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20160804/c8d81ff7/attachment.html