On 11 May 2007, at 12:37, Stian Soiland wrote:
I'm using the test-jar mechanism to share common classes for tests,
between different modules of a larger project. The main idea is to
do database and server start-ups in the common classes, but avoid
distributing them in the main JARs.
(..)
So the problem is that module 3b won't pick up that module 2's test
jar also requires module 1's test jar. However, if I in module 2's
pom remove <scope>test</scope> everything works. I believe this is
because module 2's test-jar depends on module 2's jar (and thereby
module 2's dependencies). I don't think this is a very good
solution as this forces any module2-users to also depend on the
module 1 tests. Hard-coding the module 1 test dependency as in
module 3a also works, but it means that the dependencies have to be
copied over manually whenever module 2 is updated.
Does anyone have any idea on this case or should I refer some other
mailing list..?
--
Stian Soiland, myGrid team
School of Computer Science
The University of Manchester
http://www.cs.man.ac.uk/~ssoiland/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
