[ https://issues.jboss.org/browse/WFWIP-188?page=com.atlassian.jira.plugin.... ] Jean Francois Denise commented on WFWIP-188: -------------------------------------------- [~brian.stansberry], that is resolvable. We could add the extra build step to all templates. The side effect is to create 2 builds and 2 images in all cases. Is it something we want? As an example, helloworld-rs qs sizing: * Built using existing template: 946MB * Built using chained build: 755MB * Built using chained build and galleon layers (cdi,jaxrs): 590MB A note on using galleon. Using galleon with existing templates (except started one) fails. Some env var are set in the template for subsystems that are not present in the set of Galleon layers. For example, basic and https templates contains JGROUPS_CLUSTER_PASSWORD that breaks launch of server if jgroups is not provisioned. So we need a new template that doesn't set any env var by default. That is the reason of the new template with a parameter used to provide galleon layers. If we decide to include chained builds in some existing templates, then the starter template could be evolved to contain a Galleon Layers parameter and remove the new template. -- This message was sent by Atlassian Jira (v7.13.5#713005)