You have to distinguish between plugin dependencies and project dependencies.
For plugin dependencies this can get solved with a new switch in the maven-plugin-plugin. But for user projects this is more complicated. E.g you yourself would not even be able to compile a bugfix version of slf4j-1.5 anymore with this new version of maven! LieGrue, strub ----- Original Message ----- > From: ceki <c...@qos.ch> > To: Maven Developers List <dev@maven.apache.org> > Cc: > Sent: Tuesday, December 11, 2012 10:13 PM > Subject: Re: Logback in Maven Core > > On 11.12.2012 21:28, Mark Struberg wrote: > >> Folks, don't you see it? we cannot use logback as this is a >> LocationAwareLogger and would break all projects which use slf4j < 1.6 >> and older. Please go back to the original mail from 4 month where >> Ceki himself explained it! > > Hi Mark, > > You are assuming that a plugin somehow sees it's own version of > slf4j-api on the class path but sees logback (the version that ships** > with Maven) instead of it's preferred logging framework. Isn't that an > overly pessimistic scenario which could not occur in practice? > > **subject to approval > >> LieGrue, >> strub > > -- Ceki > 65% of statistics are made up on the spot > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org