Our tc.test-compile module has a dependency on spring-hibernate3,  
which in turn apparently has a dependency on Hibernate 3.1.2.  The tim- 
system-tests-parent module depends on tc.test-compile.

This means that our tim-hibernate-3.2.5-system-tests actually run  
against Hibernate 3.1.2.  This shows up in a couple of ways, but one  
of them is that in that test project, the generated target/runtime- 
classpath.txt includes hibernate-3.1.2.jar, not hibernate-3.2.5.jar.

I have a couple of questions:

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.

2. What can I do to fix this?  (I.e., how are version conflicts  
managed in Maven?)

3. Will someone shoot me now, please?

Thanks,
   -walter
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev

Reply via email to