Currently the jbpm-enterprise-jee5 module builds two different jars, one for EAP 4.3 and the other for EAP 5. The POM file relies on profiles to create one or the other. This is bad practice as the resulting jars share a common artifactId even though they take different final names. They should be distinguished by classifier.

The proposal here is to make the EAP5-compatible artifact the primary one, since 5 is the latest EAP version. The EAP4-compatible artifact is to be classified "eap4". Among the advantages of the new arrangement are the ability to reference each artifact separately through the classifier, and the ability to build both jars in the same Maven build.