On Fri, Feb 26, 2010 at 1:29 PM, Nico Tromp <nico.tr...@gmail.com> wrote: > Jeppe, > > as far as I know this can be handled by setting the scope for slf4j- > log4j to 'test' and for logback-classic to "compile". > Or am I missing your point.
scope=compile (which is the default) also puts the dependency on the test classpath. From maven.org compile This is the default scope, used if none is specified. Compile dependencies are available in all classpaths of a project. Furthermore, those dependencies are propagated to dependent projects. > What do you mean with generated POM dependencies in 3? This is the pom for lift-common. People depending on lift-common should not see slf4j-logj4 or logback-classic. They are only used for compiling lift-common.jar (which works for scope=provided, but they are still both included on the test classpath) /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
