Currently, WFC is build and tested against a specific version of EAP (down to the micro). This is because the Camel subsystem creates dependencies on module from the the base layer that only work for those specific EAP modules with that specific content.

To make WFC portable across an array of EAP versions, we must document the necessary set of dependencies on EAP and get agreement from EAP to keep the content of these modules stable within agreed portability boundaries. Likewise, Camel would also have to agree to keep its dependencies on EAP stable within agreed portability boundaries.

The compatibility contract is here and also documented (including specific versions) here