Sooner (rather then later), a BRMS version will need to go into the customer Maven Enterprise Repository (Project Wolf). This will probably happen some time after the release, when it's impossible to change the release.

BRMS 5.3 probably can't get into Wolf because of mvel, see below for details. Unless we fix this, future versions will have the same problem.



Sooner or later, the droolsjbpm artifacts and all of their dependencies
will have to be deployed to the JBoss Maven Enterprise Repository (AKA project Wolf).
And it's far more stricter then the JBoss Maven Community Repository.
From the mail of team wolf:
> Without this review and approval your
> Maven artifacts must not be released publically nor be permitted into
> the hosted Maven Enterprise Repository.
I doubt if our mvel version names of "2.1.0.drools8", "2.1.0.drools9", ... will pass,
preventing all of droolsjbpm to be deployed to Wolf.

One solution is to release mvel "2.1.0.Final", "2.1.1.Final", ... for drools 5.5.x
so it follows the pattern major.minor.micro.[Alpha[n]|Beta[n]|CR[n]|Final], outlined here:
  https://community.jboss.org/wiki/JBossProjectVersioning