<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 6/16/2015 8:36 AM, Tomaž Cerar
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAMquZP427YXr=02Pe0ZtS7baESdxQT3_yyqHmLt0p-2i_NdK+w@mail.gmail.com"
      type="cite">
      <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>
        </div>
      </div>
    </blockquote>
    That's an OK approach if there is a well-defined base of modules
    that several projects use.   But that's really not the case.<br>
    <br>
    In any feature pack I should be able to just list the artifacts I'm
    using and it provides a default module.xml file for that.<br>
    <blockquote
cite="mid:CAMquZP427YXr=02Pe0ZtS7baESdxQT3_yyqHmLt0p-2i_NdK+w@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><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">&lt;<a moz-do-not-send="true"
              href="mailto:ssilvert@redhat.com" target="_blank">ssilvert@redhat.com</a>&gt;</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>
            &gt; Module definition is now done in 3 places?  Copies of
            one another?<br>
            &gt;<br>
            &gt; eap6-service-overlay<br>
            &gt; server-feature-pack<br>
            &gt; adapter-feature-pack<br>
            &gt;<br>
            &gt; This is very very error prone guys.  I guarantee
            somebody will forget to<br>
            &gt; update something.<br>
            &gt;<br>
            &gt;<br>
            <br>
            _______________________________________________<br>
            wildfly-dev mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
            <a moz-do-not-send="true"
              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>
    </blockquote>
    <br>
  </body>
</html>