<!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">
    That's a fair point, however to address this (and for simplicity's
    sake) what if we were to provide a combined jar that included most
    of the modules?&nbsp; I would say that the following list represents the
    "core" of Seam:<br>
    <br>
    Solder<br>
    Catch<br>
    Config<br>
    International<br>
    JMS<br>
    Mail<br>
    Persistence<br>
    REST<br>
    Security<br>
    Servlet<br>
    Validation<br>
    <br>
    We would simply call this combined jar seam.jar, and on top of that,
    the developer would also add dependencies for whatever view
    technology they're using (i.e. seam-faces, errai or seam-wicket),
    and then the extra features if they require them (Cron, JCR,
    Remoting, Reports, Social, etc).&nbsp; That should greatly reduce the
    number of jar files in a deployment.<br>
    <br>
    On 10/06/11 08:08, John D. Ament wrote:
    <blockquote
      cite="mid:BANLkTinDcR-YvYvoxd1pW-eBK20PyJE7Tg@mail.gmail.com"
      type="cite">-1<br>
      <br>
      In my opinion the combined jar helps keep the number of JAR files
      down in deployments.<br>
      <br>
      <div class="gmail_quote">On Thu, Jun 9, 2011 at 12:54 AM, Dan
        Allen <span dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:dan.j.allen@gmail.com">dan.j.allen@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;">+1
          <div><br>
          </div>
          <div>-Dan
            <div>
              <div class="h5"><br>
                <br>
                <div class="gmail_quote">On Thu, Jun 9, 2011 at 00:12,
                  Jason Porter <span dir="ltr">&lt;<a
                      moz-do-not-send="true" href="http://lightguard.jp"
                      target="_blank">lightguard.jp</a>@<a
                      moz-do-not-send="true" href="http://gmail.com"
                      target="_blank">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;">+1
                    <div>
                      <div><br>
                        <br>
                        <div class="gmail_quote">On Wed, Jun 8, 2011 at
                          17:32, Shane Bryzak <span dir="ltr">&lt;<a
                              moz-do-not-send="true"
                              href="mailto:sbryzak@redhat.com"
                              target="_blank">sbryzak@redhat.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;">
                            We discussed this briefly on IRC, however I
                            thought we should discuss it<br>
                            on seam-dev before we make any concrete
                            decision. &nbsp;To summarise the plan:<br>
                            <br>
                            1. Remove the combined jar file from each of
                            the modules<br>
                            2. If the module has a single
                            implementation, rename it to whatever the<br>
                            combined jar was called.<br>
                            &nbsp; &nbsp; E.g. for Seam Catch, the impl module
                            would be called seam-catch.<br>
                            3. If the module has multiple
                            implementations, then add a suffix to the<br>
                            artifact name that reflects the individual
                            implementation.<br>
                            &nbsp; &nbsp; E.g. Seam Reports has two
                            implementations, which would be called<br>
                            seam-reports-jasper (for Jasper reports) and
                            seam-reports-pentaho (for<br>
                            Pentaho).<br>
                            4. Leave the API naming as it is, e.g.
                            seam-reports-api.<br>
                            <br>
                            The idea is that by importing the simplified
                            module artifact name (i.e.<br>
                            "seam-xxx") you would get the default
                            implementation, which in turn<br>
                            depends on the API. &nbsp;The advantage of this
                            is that we won't break<br>
                            backwards compatibility - e.g. someone
                            currently declaring a dependency<br>
                            on "seam-catch" in their pom file won't have
                            their app broken when we<br>
                            rename the modules. &nbsp;Also we remove the
                            complexity introduced by having<br>
                            a combined jar in the first place.<br>
                            <br>
                            If you can spot any issues with this, please
                            speak up now ;)<br>
                            <br>
                            Shane<br>
_______________________________________________<br>
                            seam-dev mailing list<br>
                            <a moz-do-not-send="true"
                              href="mailto:seam-dev@lists.jboss.org"
                              target="_blank">seam-dev@lists.jboss.org</a><br>
                            <a moz-do-not-send="true"
                              href="https://lists.jboss.org/mailman/listinfo/seam-dev"
                              target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
                          </blockquote>
                        </div>
                        <br>
                        <br clear="all">
                        <br>
                      </div>
                    </div>
                    -- <br>
                    Jason Porter<br>
                    <a moz-do-not-send="true"
                      href="http://lightguard-jp.blogspot.com"
                      target="_blank">http://lightguard-jp.blogspot.com</a><br>
                    <a moz-do-not-send="true"
                      href="http://twitter.com/lightguardjp"
                      target="_blank">http://twitter.com/lightguardjp</a><br>
                    <br>
                    Software Engineer<br>
                    Open Source Advocate<br>
                    Author of Seam Catch - Next Generation Java
                    Exception Handling<br>
                    <br>
                    PGP key id: 926CCFF5<br>
                    PGP key available at: <a moz-do-not-send="true"
                      href="http://keyserver.net" target="_blank">keyserver.net</a>,
                    <a moz-do-not-send="true" href="http://pgp.mit.edu"
                      target="_blank">pgp.mit.edu</a><br>
                    <br>
                    _______________________________________________<br>
                    seam-dev mailing list<br>
                    <a moz-do-not-send="true"
                      href="mailto:seam-dev@lists.jboss.org"
                      target="_blank">seam-dev@lists.jboss.org</a><br>
                    <a moz-do-not-send="true"
                      href="https://lists.jboss.org/mailman/listinfo/seam-dev"
                      target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
                    <br>
                  </blockquote>
                </div>
                <br>
                <br clear="all">
                <br>
                -- <br>
              </div>
            </div>
            <div>Dan Allen</div>
            Principal Software Engineer, Red Hat | Author of Seam in
            Action<br>
            Registered Linux User #231597<br>
            <br>
            <div><a moz-do-not-send="true"
                href="http://www.google.com/profiles/dan.j.allen#about"
                target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>
              <a moz-do-not-send="true" href="http://mojavelinux.com"
                target="_blank">http://mojavelinux.com</a><br>
              <a moz-do-not-send="true"
                href="http://mojavelinux.com/seaminaction"
                target="_blank">http://mojavelinux.com/seaminaction</a><br>
            </div>
            <br>
          </div>
          <br>
          _______________________________________________<br>
          seam-dev mailing list<br>
          <a moz-do-not-send="true"
            href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
          <a moz-do-not-send="true"
            href="https://lists.jboss.org/mailman/listinfo/seam-dev"
            target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
          <br>
        </blockquote>
      </div>
      <br>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
seam-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/seam-dev">https://lists.jboss.org/mailman/listinfo/seam-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>