title: In a multi-module project, can a maven module access transitive test-scoped dependencies of another module it depends on?
body: <p>I have a multi-module Maven+Spring project. Some modules depend on other modules.</p>
  
  <p>Let's say we have a module named <code>services</code> that depends on the module named <code>persistence</code>.</p>
  
  <p>The services module :</p>
  
  <ul>
  <li>At Spring level, imports the <code>persistence</code> context</li>
  <li>At Maven level, depends on the <code>persistence</code> module</li>
  </ul>
  
  <p>The <code>persistence</code> module defines some configuratrion related to the... persistence : datasource, JPA, transactions... </p>
  
  <p>It has some dependencies for testing the DB (JDBC drivers, DBCP, H2) that are limited to the test scope, since when the app is deployed, the DataSource will defined in the container (Tomcat) and accessed via JNDI.</p>
  
  <p>Now, I would like to have access, during the Maven test phase of the <code>services</code> module, to the test-scoped (transitive) dependencies of the <code>persistence</code> module.</p>
  
  <p>The <a href="http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-project-dependencies.html" rel="noreferrer">Maven manual (Table 3.1)</a> say that normally, test-scope dependencies are not available transitively.</p>
  
  <p>Is it  possible to obtain them somehow in the context of a multi-module project ?</p>
  
  <p>If not what are good alternatives ? (Define the test dependencies in the parent pom ?... )</p>