Well, there's currently no notion of runtime dependencies so test dependencies is the closest we have.
alex On Monday, January 17, 2011, John Shahid <[email protected]> wrote: > Well I'd expect in this instance to add slf4j or commons logging to the > compile dependencies and log4j to the runtime dependencies. I think it makes > more sense to include compile dependencies instead of test.compile. What do > you think ? > > On Sun, Jan 16, 2011 at 11:20 PM, Alex Boisvert > <[email protected]>wrote: > >> I thought it would be a better default. Test dependencies usually >> include addional dependencies to run the software (i.e., compile >> against inteface, run against implementation.) A concrete example >> would be compiling against SLF4J and running against Log4J. >> >> alex >> >> On Saturday, January 15, 2011, John Shahid <[email protected]> wrote: >> > Hey all, >> > >> > I came across lines 174-177 in lib/buildr/run.rb >> > >> > after_define(:run => :test) do |project| >> > project.run.with project.test.compile.dependencies >> > project.run.with project.test.compile.target if >> project.test.compile.target >> > end >> > >> > My question is why are the dependencies used in compiling the tests added >> to the run task ? >> > >> >
