Hide Forgot
+++ This bug was initially created as a clone of Bug #1038794 +++ Description of problem: As best I can tell the EAP 6.2 content reused the same channels as 6.0 and 6.1. This means as soon as the Online nodes are updated the EAP cartridge manifest.yml and https://www.openshift.com/developers/technologies will be inaccurate. I believe this has been discussed in the past, but I believe it would be best to only state the version as 6 in the manifest's display name to avoid this for EAP minor releases.
https://www.openshift.com/developers/technologies has already been updated for OSE.
We might actually put 6.2.0 in the display-name simply to inform users of the version of EAP that we support. There's no longer an easy way for customers to install an RPM'd version of EAP 6.1.0 from RHN so we aren't going to be able to easily support anything other that 6.2.0.
https://github.com/openshift/enterprise-server/pull/184 Next version of openshift-origin-cartridge-jbosseap
Doesn't look like this has been built yet. We'll ship this with our next minor update.
Building for 2.0.1.
Verify this on package openshift-origin-cartridge-jbosseap-2.11.1.2-1.el6op.noarch It shows: Display-Name: JBoss Enterprise Application Platform 6 in the manifest.yml.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0020.html