Description of problem: Connected issue: https://bugzilla.redhat.com/show_bug.cgi?id=1264840 Currently CDI package contains references to both Remote and Embedded JDG classes. This causes many problems like BZ1264840. The best way to deal with it is to split Uber Jar CDI package into two pieces - remote and embedded.
Sebastian Łaskawiec <slaskawi> updated the status of jira ISPN-5838 to Coding In Progress
Backward INcompatible (but ideal) tracked here: https://issues.jboss.org/browse/ISPN-5900
*** Bug 1268894 has been marked as a duplicate of this bug. ***
As Sebastian said, this cannot be fixed without breaking backwards compatibility.
Just an extended version why we can not do it: The implementation would require moving classes from org.infinispan.cdi package into org.infinispan.cdi.remote and org.infinispan.cdi.embedded which would break client's code. Therefore we can not do it in minor release.
In JDG 6 series we managed to split the extension into two parts - Embedded and Remote. However we decided to leave java packaging as it was before (in org.infinispan.cdi). This fixes unnecessary dependencies for those jars and gives our client a choice - what kind of functionality they need. Proper solution for JDG is tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1278449
*** This bug has been marked as a duplicate of bug 1278449 ***