On Monday 27 October 2008 08:09:41 pm Walter Harley wrote:
> 1. Why does tc.test-compile depend on spring-hibernate3? I'd have
> thought individual projects that needed Spring would have their own
> explicit dependency.
The original dependencies for our Maven artifacts were formulated by taking
the union of all dependencies of all modules that went into the artifacts.
What that means is that, for any module that contributed any classes to the
tc.test-compile Maven artifact, we looked at the existing dependencies in the
ivy*.xml files and simply added them as dependencies for the new Maven
artifact. It is quite possible, even likely, that some of those dependencies
were for test cases only and not true dependencies of the test framework code
that makes up tc.test-compile.
I'll revisit the dependencies for tc.test-compile and remove anything that
looks suspicious. If the artifacts still compile and the tests still pass,
I'll commit.
> 2. What can I do to fix this? (I.e., how are version conflicts
> managed in Maven?)
Alex has already mentioned the use of exclusions to work around the version
conflicts.
> 3. Will someone shoot me now, please?
mvn gun:shoot -Dtarget=walter
Now you just have to wait for Maven to download the Internet. ;-)
--
Jason Voegele
The older I grow, the more I distrust the familiar doctrine that age
brings wisdom.
-- H. L. Mencken
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev
