It shouldn't be that test dependencies don't work - it's just that if you create a jar from your tests, there is no separation about what its dependencies are.
The best workaround which is still encouraged regardless is to separate your reusable test code into a library of its own instead. - Brett On 11/3/05, Barry Kaplan <[EMAIL PROTECTED]> wrote: > Since I have a ton of test dependencies to manage, is there any > recommended workaround? > > What I thinking of doing is simply not using tests dependencies, and > creating a issue to go back and change them once maven adds support for > test dependencies. Another option that I might consider (but it really > smells of maven1) is to define test dependencies in a snippet file and > use an entity-include to suck them in. > > -barry > > --------------------------------------------------------------------- > 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]
