pom dependencies not added to compile Classpath
Key: MNG-725
URL:
Project: Maven 2
Type: Bug
Reporter: Jesse McConnell
I am trying to use a meta dependency pom file to lump several dependencies together into one unit.
on the webserver I have
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>meta-dependency</groupId>
<artifactId>oracle</artifactId>
<packaging>pom</packaging>
<version>1.0</version>
<name>oracle meta dependencies list</name>
<dependencies>
<dependency>
<groupId>oracle</groupId>
<artifactId>oracle</artifactId>
<version>9201</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>oracle</groupId>
<artifactId>oracle_nls_charset</artifactId>
<version>9201.12</version>
<scope>provided</scope>
</dependency>
</dependencies>
</project>
in the local pom I have:
<dependency>
<groupId>meta-dependency</groupId>
<artifactId>oracle</artifactId>
<version>1.0</version>
<type>pom</type>
</dependency>
Note: I had to specify <type>pom</here otherwise it defaulted to trying to find a .jar file for it even though the <packaging>pom</was specified in the remote pomthis seemed redundent and unnecessary. In this case the DEBUG showed it as oracle:jar:1.0 even though the remote pom was clearly in my local repo and was the one from the server, not a default one like kenney had mentioned might be the case on irc.
[DEBUG] xml-apis:xml-apis:jar:2.0.2 (selected for provided)
[DEBUG] meta-dependency:oracle:pom:1.0 (selected for compile)
[DEBUG] jclass:pagelayout:jar:5.0 (selected for provided)
that is the debug output from the compiler, I would expect to see the dependencies in the remote pom listed just below the pom declaration.
I initially tried this with <dependencyManagement injecting the version into the subproject pom, and that was the same deal.