title: Why do the JBoss/wildfly BOMs not contain all of the provided modules?
body: <p>Wildfly 8.x ships with BOMs for easy dependency management:  <a href="https://github.com/wildfly/boms" rel="nofollow">https://github.com/wildfly/boms</a></p>
  
  <p>These are useful for the module-based classloading described here:  <a href="https://docs.jboss.org/author/display/WFLY8/Implicit+module+dependencies+for+deployments" rel="nofollow">https://docs.jboss.org/author/display/WFLY8/Implicit+module+dependencies+for+deployments</a></p>
  
  <p>However, when I look in <code>$JBOSS_HOME\modules\system\layers\base</code>, I see many, many more included modules.  For example, dozens of <code>org.apache</code> modules like commons-lang, etc. are included.</p>
  
  <p>These deps are also not in the JBoss parent POM:  <a href="https://github.com/jboss/jboss-parent-pom" rel="nofollow">https://github.com/jboss/jboss-parent-pom</a></p>
  
  <p>Nor the Java EE specs:  <a href="https://github.com/jboss/jboss-javaee-specs" rel="nofollow">https://github.com/jboss/jboss-javaee-specs</a></p>
  
  <p>For these dependencies (ones not in the BOMs or in the docs), how is the developer supposed to know they are provided?  What is the intended dependency management strategy for developers using tools like Maven, etc.</p>