> A plugin declaring a dependency on slf4j-api without declaring a > dependency on an implementation does not makes sense imo. It follows > that the term "declaring a dependency on slf4j" means a dependency on > both slf4j-api as well as a binding, aka implementation.
If the get the slf4j logger injected they would only have a slf4j-api dependency, wouldn't they? I'm asking as I *think* we said we would use slf4j as the logging interface in Maven. What I'm thinking is that the aim is to allow plugins to use the core slf4j logging, right? But we would like to keep any existing behavior where a plugin logs to it's own logging file through slf4j, right? So then we can't check on a slf4j-api dependency, but need to look for an impl. Just trying to follow the discussion.... /Anders > >> /Anders > > > -- > 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
