avro-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Carey <sc...@richrelevance.com>
Subject Re: Dependencies in pom aggregation
Date Tue, 05 Jul 2011 22:57:42 GMT
Maven can work with a 'test' dependency, by declaring the dependency of
type "test-jar".


Unfortunately there are some bugs in various Maven plugins so we have been
avoiding using test-jars for now.  In particular, if you use a test-jar
and then do:

$ mvn clean
$ mvn compile

with no 'install' and no artifacts in your local repo, it may fail, trying
to resolve and pull the test dependency during compile.  This is not the
fault of the test-jar or dependency declaration, but bugs in various other
plugins in our toolchain, see


On 7/5/11 2:52 PM, "Jeremy Lewi" <jeremy@lewi.us> wrote:

>I'm working on the apache avro project and I'm having a problem with
>maven that I was hoping to get some help with.
>My project consists of several modules, one of which is "mapred".
>Now I can build "mapred" just fine e.g by doing mvn package from within
>the project.
>Another module in the project is "tools". This module depends on the
>"mapred" module. So its pom file declares the artifact for mapred as a
>dependency. So far so good.
>The problem is I would like to make the test class in the "tools"
>modules depend on the "test" classes in "mapred". So I would like to
>build a jar in "mapred" containing the "test" classes and then declare
>this as a dependency for the test classes in "tools".
>In the mapred module I can build a jar  containing the test classes
>by doing mvn jar:test-jar but I'm not sure how to add this jar as a
>dependency for the "tools" module during testing.

View raw message