Thanks. That worked great.
For posterity here is the code
Cheers,
-- Chris
pom.xml
.....
<dependency>
<groupId>com.foobar</groupId>
<artifactId>foo</artifactId>
<type>rnc</type>
<version>${fooVersion}</version>
</dependency>
<dependency>
<groupId>com.foobar</groupId>
<artifactId>bar</artifactId>
<type>rnc</type>
<version>${barVersion}</version>
</dependency>
....
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<includeTypes>rnc</includeTypes>
<outputDirectory>${project.build.directory}/
classes</outputDirectory>
</configuration>
</execution>
</executions>
</plugin>
On Mar 24, 2008, at 5:28 PM, Brian E. Fox wrote:
Unless I've misunderstood you, the standard maven-dependency-plugin
does
what you want:
http://maven.apache.org/plugins/maven-dependency-plugin/
See the "dependency-copy" goal in particular.
[cwb] this is not really sufficient. We want
1) to use <dependency> elements, so that the dependency is clearly
expressed in the POM (rather than buried in the plugin config)
2) to have the artifact copied to the local repo (for reuse) AND to
target/classes
Use dependency:copy-dependencies instead. This will copy all
dependencies of the current project, but you can filter it down to a
specific artifact that you want.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
