<div dir="ltr"><div><div><div><div><div><div>A feature-pack can extend another feature pack,<br></div>I am sure you guys know that.<br><br></div>so you could have "keycloak-base" feature pack that all other 3 extend.<br></div><br></div>the base would than have all common modules defined.<br></div>and other 3 extra specializations.<br><br>--<br></div>tomaz<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 16, 2015 at 2:18 PM, Stan Silvert <span dir="ltr"><<a href="mailto:ssilvert@redhat.com" target="_blank">ssilvert@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Cross-posting to wildfly-dev.<br>
<br>
It sounds like we need a way to standardize module.xml definitions<br>
across projects and have them accessible from maven GAV's. These<br>
module.xml files are rarely different between projects and it doesn't<br>
make sense for each feature pack to define its own copy.<br>
<br>
On 6/15/2015 4:08 PM, Bill Burke wrote:<br>
> Module definition is now done in 3 places? Copies of one another?<br>
><br>
> eap6-service-overlay<br>
> server-feature-pack<br>
> adapter-feature-pack<br>
><br>
> This is very very error prone guys. I guarantee somebody will forget to<br>
> update something.<br>
><br>
><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>