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?
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.
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.
[]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
If the patch needs to be upstream first, the
upstream build can be used to verified it, no?
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