title: JBoss Maven BOMs and transitive dependencies
body: <p>I'm trying to use a number of the BOMs in the org.jboss.bom group to bring in the API stacks that are compatible with EAP 6.3.0. My understanding is, that's what they're for. But when I reference them (using 'provided' or even 'compile' scope), the dependencies don't become transitively available. Given that "compile" scope is used on the items inside the BOMs, <a href="https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html" rel="nofollow">Maven's documentation</a> of the dependency mechanism seems to indicate that those items should be added to the classpath of my project. Yet I'm getting undefined symbols for the classes that should be brought in.</p>
  
  <p>For example, in project P, I'm including org.jboss.bom.wfk:jboss-javaee-6.0-with-spring:2.4.0-redhat-2 with 'provided' scope, yet org.springframework.context.ApplicationContext is undefined in P.</p>
  
  <p>This is all happening in JBoss Dev Studio 8.1.0.GA, if that makes a difference.</p>