On Mon, May 11, 2009 at 9:48 AM, Todd Thiessen <[email protected]> wrote:
> > > Are there many cases where you want something for compilation > > that isn't needed at runtime? I don't see them as being separate. > > Really? I am surprised. Yes there is a relation between compile and > runtime. However, there is a different relation between compile and > test. Scope has multiple meanings here. You have scope which defines > when a dependency is needed (ie: at compile or runtime); or scope that > defines what code a dependency is needed for (ie: test or main). Really, > test scope means compile time (the when dimension of scope) for test > code (the what code dimension of scope). > > For instance, how does one define a test dependency that is only needed > at runtime? Two different concepts stored in one variable makes this > cumbersome. > At test runtime I presume? You use the test scope. Is it hurting anything if it's there on the test compile classpath? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
