We'll need to support EAP5.1 when its released. Prior to release we should test with beta's etc to make sure we have no regressions. In particular we should bundle the HornetQ plugin into JON builds, and test that it plays nicely with the jbas5 plugin (which supports JBoss Messaging), and that both plugins work appropriately given which messaging provider is enabled in EAP.
HornetQ plugin: https://anonsvn.jboss.org/repos/jbossas/trunk/hornetq-int/
Note, they haven't even created a branch for EAP 5.1 yet. From what Jason G said, they plan to create the branch as soon as EAP 5.0.1 (which is actually a CP) is out the door.
We should also test against EAP 5.0.1 once it's released (or ideally before) - discovery and management, but also installing the CP via JON on top of an existing EAP 5.0 install.
ips - what needs to be done here?
EAP 5.1 GA still isn't out, but CR3 was recently released. It would be good to test RHQ against CR3 to flush out any RHQ, or EAP 5.1, bugs.
5.1 CR3 can be downloaded here: http://download.devel.redhat.com/devel/candidates/JBEAP5.0.0/JBEAP-5.1.0-CR3/
5.0.1 GA can be downloaded here:
AFAIK, 5.0.1 has not yet been released in the form of a CP for 5.0, due to technical issues with the CSP.