including something at compile-time and not test time is a rare thing for maven, which assumes tests also need dependencies used to compile. Of all the scopes you can specify for dependencies *all* of them end up on the testing classpath. (see http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html )
I would recommend droping one of your requirements, or giving us some more information on exactly the nature of the problem, so we can better assist your maven usage! - Josh Suereth ANyway, what you want to do is exclude the dependency On Fri, Feb 26, 2010 at 3:55 AM, Jeppe Nejsum Madsen <je...@ingolfs.dk>wrote: > Hi, > > For the new logging code I need a setup that I can't really see how to > achieve with Maven: > > 1) Both slf4j-log4j and logback-classic needs to be on the classpath > when compiling > 2) Only sf4j-log4j should be on the classpath when testing > 3) None should be included in the generated pom dependencies > > Using scope=provided takes care of 1) & 3) But both are still included > in the classpath during test > > /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<liftweb%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > > -- 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.
