<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    np :) Thanks for the feed-back: it's better to question too much
    then too little.<br>
    If you find anything else you think we can improve, let us know.<br>
    <br>
    Op 13-03-12 00:01, Justin Holmes schreef:
    <blockquote
cite="mid:CABU_7eXCBh_-WRwjo8SpeHBRuZnzuxpcYdxSy0kfoEKEbMyc2Q@mail.gmail.com"
      type="cite">Geoffrey,
      <div><br>
      </div>
      <div>Thanks for the explanation. Looking at this through
        the&nbsp;lens&nbsp;of git, it makes a lot more sense.</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>Best Regards,</div>
      <div>Justin</div>
      <div><br>
        <br>
        <div class="gmail_quote">
          On Sat, Mar 10, 2012 at 5:01 AM, Geoffrey De Smet <span
            dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:ge0ffrey.spam@gmail.com">ge0ffrey.spam@gmail.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
            0.8ex; border-left: 1px solid rgb(204, 204, 204);
            padding-left: 1ex;">
            <div text="#000000" bgcolor="#ffffff"> Hi Justin,<br>
              <br>
              Take a look at those intermediate aggregator poms (for
              example drools-multiproject) per git repo.<br>
              You 'll see they contain some stuff we can't do without:<br>
              <ul>
                <li>Location of JBoss repository</li>
                <ul>
                  <li>required to find and download the
                    droolsjbpm-parent pom (because that's in a different
                    repo)<br>
                  </li>
                  <li>so the build works out-of-the-box (very important
                    for getting the community involved)<br>
                  </li>
                </ul>
                <li>Repo specific overwrites that apply to all of the
                  modules in that repo but not in the others</li>
                <ul>
                  <li>dependency versions sometimes (these are temporary
                    hacks that must be removed but there are always
                    some)</li>
                  <li>plugin configurations</li>
                  <li>&lt;scm&gt; info to find the git repo</li>
                  <li>...<br>
                  </li>
                </ul>
              </ul>
              <br>
              Op 07-03-12 16:49, Justin Holmes schreef:
              <blockquote type="cite">
                <div>
                  <div class="h5">
                    <p>Hello Devs,</p>
                    <p>I'm currently working on a project where I'm
                      embedding Drools inside my application and using
                      Maven to pull down the necessary artifacts.&nbsp;During
                      this exercise, I've noticed that each project's
                      pom (e.g. drools-core) references an aggregator
                      pom (e.g drools-multiproject) as its parent. These
                      aggregators then reference droolsjbpm-parent as
                      their parent. I'm no maven expert, but it seems to
                      me that this introduces an unnecessary layer of
                      artifacts in the maven repository. My
                      understanding is that aggregators are present
                      solely to propagate build commands to their
                      children and do not contain dependency information
                      (as is the case in the Drools aggregators), so
                      shouldn't the project poms reference
                      droolsjbpm-parent directly?&nbsp;</p>
                    <p><br>
                    </p>
                    <p>Thanks,</p>
                    <p>Justin</p>
                  </div>
                </div>
                <pre><fieldset></fieldset>
_______________________________________________
rules-dev mailing list
<a moz-do-not-send="true" href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a>
<a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><span class="HOEnZb"><font color="#888888">
</font></span></pre>
                <span class="HOEnZb"><font color="#888888"> </font></span></blockquote>
              <span class="HOEnZb"><font color="#888888"> <br>
                  <pre cols="72">-- 
With kind regards,
Geoffrey De Smet</pre>
                </font></span></div>
            <br>
            _______________________________________________<br>
            rules-dev mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
            <a moz-do-not-send="true"
              href="https://lists.jboss.org/mailman/listinfo/rules-dev"
              target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
rules-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
With kind regards,
Geoffrey De Smet</pre>
  </body>
</html>