We encounter many poorly packaged jars.

We would like to scan the ear for jar files that are either already in a JBoss module or should be or should be left out.

Examples:
1. hibernate.jar, servlet.jar, infinispan.jar There is no reason to include either of these in production.
2. JAXB - included in JBoss, if this needs to be included because of version issue then it should go into a module.

Reason:
1. Decompiling and loading these into the graph wastes a huge amount of time in the tool. Having list of files to ignore because they shouldn't be in the ear in the first place will shorten run time, even on large ear files.

2. It will teach them about the modularity of JBoss

3. Their apps will deploy and startup faster on JBoss reinforcing image of high performance.

4. This is something so simple a caveman could do and thus it gives an assignment to the least capable member of the migration team and keeps them from mucking about.