[ https://issues.jboss.org/browse/WFLY-10335?page=com.atlassian.jira.plugin... ] Stuart Douglas commented on WFLY-10335: --------------------------------------- So to elaborate a bit the main reason behind this is that WildFly is different to a lot applications that are build using maven. If you are building a standard application you have one copy of each relevant descriptor, if you have special test version of them it is fine to have them in src/test/resources, as they are used for all tests. WildFly is not like this, every test has its own deployment descriptors. There is simply no point in having a mirrored package structure, it just means that you need to look at multiple locations to fully understand a test, and generally complicates the code base. In general we will follow maven conventions unless there is a good reason not to, and in this case the benefit of having all test resources being self contained is a lot more important that following the maven conventions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)