For official EAP support issues, please go through Red Hat support channel. In this community JBeret space, we are happy to discuss issues and provide best-effort help with no SLA.
We currently have plan to upgrade JBeret in WildFly: [WFLY-10662] Upgrade JBeret from 1.3.0.Final to 1.3.1.Final - JBoss Issue Tracker
In the pull request details, you can examine what changes are.
There is also plan to patch JBeret in EAP: [JBEAP-14952] [GSS](7.1.z) Upgrade jberet to 1.2.6.Final - JBoss Issue Tracker
Hope that helps.
I think my question was misleading as its not an official support request: I was just wondering if it would be possible to replace an existing JBeret module with a newer one.
From your answer I assume that this is not possible as it need developer effort to provide a JBeret module with a newer version in a eap. So I would think that if I want to use a newer JBeret version
then I will have to go with wildfly instead of eap?
For JBoss EAP in production, I would not recommend replacing jberet module with newer version, since it may cause unexpected behavior and make it unsupportable. For development use, whether a newer version of jberet-core module works in your EAP or WildFly installation varies case by case. In general, if the vesion numbers are close, then it's more likely to work, by simply replacing jberet-core jar file, and updating the jberet-core version number in the module.xml for jberet-core module.
one last question on this: replacing the jberet-core jar will probably not give me the brand new admin interface you announced recently?
Replacing jberet-core will not affect WildFly Admin Console.