This module was always meant to make it possible to swap in a dependency of different versions of Infinispan than the one normally included in the application server,

So instead of the container provided Infinispan version, we want to be able to also bundle an Infinispan version with the application which should then be used instead?

but the current module layout is rather leaky it seems;

What do you mean with that?

this might conflict with the Infinispan version used by Hibernate ORM and needs to be isolated,

How? Are you saying that there are potentially three Infinispan versions? Where is ORM using Infinispan anyways? As second level cache, right? ORM uses in this case the container bundled Infinipspan version, right (or can it use its own as well)?

but we still want to be able to start it by loading custom resources (configuration files).

why is that a problem?