Hi there,
The URL https://github.com/jbossas/jboss-eap returns 404. I can find only as tags and releases, no eap.
So the only way to get sources for EAP is waiting for Red Hat to release the zip file at
ftp://ftp.redhat.com/redhat/jbeap/
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.
Am I right?
[]s, Fernando Lozano… and where is upstream for EAP-6.x ?I think it is jboss-eap/6.x, and not jboss-as/7.1On Apr 17, 2013, at 1:04 PM, Heiko Braun <hbraun@redhat.com> wrote:If the patch needs to be upstream first, the upstream build can be used to verified it, no?On Apr 17, 2013, at 1:02 PM, Thomas Diesler <thomas.diesler@jboss.com> wrote:All would be good if the reporter can verify the patch before it goes in the next EAP release, can he?xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler JBoss OSGi Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx_______________________________________________ jboss-as7-dev mailing list jboss-as7-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
[]s, Fernando Lozano
… and where is upstream for EAP-6.x ?
I think it is jboss-eap/6.x, and not jboss-as/7.1
On Apr 17, 2013, at 1:04 PM, Heiko Braun <hbraun@redhat.com> wrote:
If the patch needs to be upstream first, the upstream build can be used to verified it, no?
On Apr 17, 2013, at 1:02 PM, Thomas Diesler <thomas.diesler@jboss.com> wrote:
All would be good if the reporter can verify the patch before it goes in the next EAP release, can he?
xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler JBoss OSGi Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ jboss-as7-dev mailing list jboss-as7-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler JBoss OSGi Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx