I am interested in this also. I'm having IlegalAccess errors using 3.2.5 because of the order JBoss deploys my EARs. I found a workaround: it seems like the default deployment scheme uses alphabetical sorting.

In JBoss EAP 7.0, annotation indexes for static modules are automatically generated, so you do not need to create them. However, you must tell the module import to use the annotations by adding the dependencies to either the MANIFEST.MF or the jboss-deployment-structure.xml file. You must know the name of the project's module dependencies. Refer to Section 3.7.2, "Included Modules" for the list of static modules included with JBoss Enterprise Application Platform 6. If the module is another deployment , then refer to Section 3.1.7, "Dynamic Module Naming" to determine the module name. The Project Object Model, or POM, file is a configuration file used by Maven to build projects. It is an XML file that contains information about the project and how to build it, including the location of the source, test, and target directories, the project dependencies, plug-in repositories, and goals it can execute. Class loading in AS7 is considerably different to previous versions of JBoss AS. Class loading is based on the JBoss Modules project. Instead of the more familiar hierarchical class loading environment, AS7's class loading is based on modules that have to define explicit dependencies on other modules. How to declare a dependency on a JBoss module in JBoss EAP 6? I created com/mysql/main under modules and placed the mysql-connector-java-5.1.35-bin.jar in there. I created a module.xml file with these contents and put that in the same directory, still When I run my application on the server it says that it can not find the driver.: Well the fact is that it work, but I find annoying that I didn't make it to work with manifest dependencies. An ideas ? This short tutorial show h