Josh Suereth <[email protected]> writes: > 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!
I kind of worked around them :-) I wanted to create helpers for both slf4j-log4j and logback-classic in the same project. But at runtime only one of them will actually be present. Having both causes slf4j to (correctly) complain about multiple bindings. Turned out it wasn't really slf4j-log4j I needed at compile time. Log4j will suffice. So only logback-classic will be included as an slf4j binding during tests...... /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
