<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 17, 2013, at 4:19 PM, Fernando Lozano &lt;<a href="mailto:fernando@lozano.eti.br">fernando@lozano.eti.br</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
  
    <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi there,<br>
      <br>
      The URL <a class="moz-txt-link-freetext" href="https://github.com/jbossas/jboss-eap">https://github.com/jbossas/jboss-eap</a> returns 404. I can
      find only as tags and releases, no eap.<br>
      <br>
      So the only way to get sources for EAP is waiting for Red Hat to
      release the zip file at<br>
      <br>
      <a class="moz-txt-link-freetext" href="ftp://ftp.redhat.com/redhat/jbeap/">ftp://ftp.redhat.com/redhat/jbeap/</a><br>
      <br>
      And customers wishing to try a patch to confirm an issue is solved
      have no way to do that, unless the developer sends them the patch
      file by other means (e-mail) and the patch file does not depends
      on any other change made to the trunk since the latest release.<br>
      <br>
      Am I right?<br></div></div></blockquote><div><br></div><div>Yes, thats it. I provide a patch to the best of my knowledge and there is no way to verify that patch until it is part of a release. The reporter can verify the release and only then report back that the patch is not valid.&nbsp;</div><div><br></div><div>Unfortunately, I don't have a good answer on how to fix this other than "make jboss-eap public". Then again, I don't really understand why it is so secret what we do there if we release eap+sources every couple of months anyway.</div><div><br></div><blockquote type="cite"><div text="#000000" bgcolor="#FFFFFF"><div class="moz-cite-prefix">
      <br>
      <br>
      []s, Fernando Lozano<br>
      <br>
      <br>
    </div>
    <blockquote cite="mid:F4A40C6E-9988-4DA2-940D-ABC381A56B99@jboss.com" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      … and where is upstream for EAP-6.x ?
      <div><br>
      </div>
      <div>I think it is&nbsp;<a moz-do-not-send="true" href="https://github.com/jbossas/jboss-eap">jboss-eap/6.x</a>,
        and not&nbsp;<a moz-do-not-send="true" href="https://github.com/jbossas/jboss-as/tree/7.1">jboss-as/7.1</a><br>
        <div><br>
          <div>
            <div>On Apr 17, 2013, at 1:04 PM, Heiko Braun &lt;<a moz-do-not-send="true" href="mailto:hbraun@redhat.com">hbraun@redhat.com</a>&gt;
              wrote:</div>
            <br class="Apple-interchange-newline">
            <blockquote type="cite">
              <meta http-equiv="Content-Type" content="text/html;
                charset=ISO-8859-1">
              <div style="word-wrap: break-word; -webkit-nbsp-mode:
                space; -webkit-line-break: after-white-space; ">
                <div><br>
                </div>
                <div><br>
                </div>
                <div>If the patch needs to be upstream first, the
                  upstream build can be used to verified it, no?</div>
                <div><br>
                </div>
                <div><br>
                </div>
                <br>
                <div>
                  <div>On Apr 17, 2013, at 1:02 PM, Thomas Diesler &lt;<a moz-do-not-send="true" href="mailto:thomas.diesler@jboss.com">thomas.diesler@jboss.com</a>&gt;
                    wrote:</div>
                  <br class="Apple-interchange-newline">
                  <blockquote type="cite"><span style="font-family:
                      Helvetica; font-size: medium; font-style: normal;
                      font-variant: normal; font-weight: normal;
                      letter-spacing: normal; line-height: normal;
                      orphans: 2; text-align: -webkit-auto; text-indent:
                      0px; text-transform: none; white-space: normal;
                      widows: 2; word-spacing: 0px;
                      -webkit-text-size-adjust: auto;
                      -webkit-text-stroke-width: 0px; display: inline
                      !important; float: none; ">All would be good if
                      the reporter can verify the patch before it goes
                      in the next EAP release, can he?</span></blockquote>
                </div>
                <br>
              </div>
            </blockquote>
          </div>
          <br>
          <div>
            <div>
              <pre class="moz-signature" cols="72">xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx </pre>
              <div><br>
              </div>
            </div>
            <br class="Apple-interchange-newline">
          </div>
          <br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
jboss-as7-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a></pre>
    </blockquote>
    <br>
  </div>

</blockquote></div><br><div>
<div><pre class="moz-signature" cols="72">xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx </pre><div><br></div></div><br class="Apple-interchange-newline">

</div>
<br></body></html>