Description of problem: In App's "jboss-deployment-structure.xml" file, customer set "exclusions" to exclude EAP's module "org.apache.httpcomponents", he used another version of those jars stored in WEB-INF/lib. Then EAP loaded module "org.jboss.resteasy.resteasy-jaxrs" when deployed App: ~~~ DEBUG [org.jboss.as.server.deployment] (MSC service thread 1-6) Adding dependency ModuleDependency [identifier=org.jboss.resteasy.resteasy-jaxrs ... ~~~ However, this module("resteasy-jaxrs") has exported "org.apache.httpcomponents": ~~~module.xml~~~ <dependencies> <module name="org.apache.httpcomponents" /> ... <!-- exported --> <module name="org.apache.httpcomponents" export="true"/> ... ~~~~~~~~~~~~~~~~ Finally, the App failed to get deployed due to use the wrong version of "org.apache.httpcomponents" and "java.lang.NoSuchMethodError" error appeared. Customer has to exclude module "resteasy-jaxrs" as well to make App deployed. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Deploy attached war to EAP 6.4 standalone. 2. review log. 3. Actual results: Expected results: Additional info: In this scenario, it seems that "exclusions" and "export='true'" is a contradiction. Please let us know do we have a workaround or any other setting to avoid it?
Created attachment 1188528 [details] 1
Created attachment 1188529 [details] 2
Created attachment 1188530 [details] 3
*** This bug has been marked as a duplicate of bug 1266122 ***