On Jul 4, 2013, at 11:12 AM, Robert Muir <[email protected]> wrote: > > > On Thu, Jul 4, 2013 at 11:09 AM, Mark Miller <[email protected]> wrote: > > On Jul 4, 2013, at 11:06 AM, Mark Miller <[email protected]> wrote: > > >> we could solve that with an ivy configuration for 'tests' instead > > Or perhaps solved by that? I don't really know what you are suggesting though > - ivy is half as mysterious as maven to me. > > > Basically you have the ability to say that src/java depends on libfoo.jar and > libbar.jar, but that src/test also needs libbaz.jar (only for running those > tests). > > It might add some complexity, but then the dependencies would be "more > correct" I think, because test-framework doesnt really have any classes that > need these dependencies (from what I see).
Yeah, it seems like that should be doable then. The tests that use those dependencies are all in solr/core - like I said, the reason they went into test-framework was to avoid having them go out as part of Solr - not because classes there use them. - Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
