<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Let's keep the same package name, as this is a major version change.
    I don't think people will run into problems, unless proven
    otherwise.<br>
    <br>
    <div class="moz-cite-prefix">On 11/20/2013 04:09 PM, Lincoln Baxter,
      III wrote:<br>
    </div>
    <blockquote
cite="mid:CAEp_U4Gyhfr=zT-r7HepSGcDknXuYzOiEw3PKOE1x+LDJAe=4g@mail.gmail.com"
      type="cite">
      <div dir="ltr">As I said in IRC, I worry that allowing both to be
        on the classpath would lead to a lot of confusing/partially
        migrated code.</div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Wed, Nov 20, 2013 at 12:30 PM, Matt
          Benson <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:gudnabrsam@gmail.com" target="_blank">gudnabrsam@gmail.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="ltr">Hi all,
              <div>&nbsp; As development continues on Forge 2, I think we had
                all hoped the improvements to the parser API would be
                available in time to be used for the release. &nbsp;We now
                have a split between JavaType and JavaSource which
                represent the read only and writable portions of the
                parser API for a given
                class|interface|enum|annotation|package-descriptor. &nbsp;The
                latest version is at&nbsp;<a moz-do-not-send="true"
                  href="https://github.com/forge/java-parser/tree/refactor-hierarchy"
                  target="_blank">https://github.com/forge/java-parser/tree/refactor-hierarchy</a>.
                &nbsp;Would it be SOP to proceed by publishing a SNAPSHOT,
                or...?</div>
              <div><br>
              </div>
              <div>&nbsp; Also, since there are quite a few incompatible API
                changes, I wonder if it would make sense to change the
                package name at some level, e.g.
                org.jboss.forge.parser2, as well as the Maven artifact
                id. &nbsp;By avoiding "jar hell" with multiple versions of
                the library on the classpath, this would make it
                possible for dependent Forge plugins to switch over
                gradually if necessary and might avoid impacting release
                timelines.</div>
              <div><br>
              </div>
              <div>Thanks,</div>
              <div>Matt</div>
            </div>
            <br>
            _______________________________________________<br>
            forge-dev mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
            <a moz-do-not-send="true"
              href="https://lists.jboss.org/mailman/listinfo/forge-dev"
              target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <div><br>
        </div>
        -- <br>
        Lincoln Baxter, III<br>
        <a moz-do-not-send="true" href="http://ocpsoft.org"
          target="_blank">http://ocpsoft.org</a><br>
        "Simpler is better."
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
forge-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/forge-dev">https://lists.jboss.org/mailman/listinfo/forge-dev</a></pre>
    </blockquote>
    <br>
  </body>
</html>