Thanks Tamás! In hindsight of backward compatibility a plugin would always need to add slf4j-api and a logging backend. Otherwise it would not run with <= mvn-3.0.4 , right? Which means that our classloader isolation trick would always trigger? Feels like I miss something...
LieGrue, strub ----- Original Message ----- > From: Tamás Cservenák <ta...@cservenak.net> > To: Maven Developers List <dev@maven.apache.org> > Cc: > Sent: Thursday, October 11, 2012 1:39 PM > Subject: Re: SLF4J integration > > Here is one with slf4j + logback: > > https://github.com/sonatype/nexus-maven-plugins/tree/master/nexus-staging-maven-plugin > > and the logging related bits (like LogbackUtils) used in mojos are here: > https://github.com/sonatype/mojo-commons > > Purpose of it: this plugin makes use of a SISU component (not maven > specific) that uses SLF4J for logging: > https://github.com/sonatype/spice-zapper > > > Again, the plugin does not use SLF4J for logging, it uses Mojo Log as > recommended by docs. > > But, the SISU component embedded and used within Mojo execution does use > SLF4J API (only!). > Clearly, logback is here to provide SLF4J backend, and is synced with Maven > logging level + some trickery as component is bit too "chatty" at INFO > level. > > https://github.com/sonatype/nexus-maven-plugins/blob/master/nexus-staging-maven-plugin/src/main/java/org/sonatype/nexus/maven/staging/deploy/strategy/ImageDeployStrategy.java#L141 > > > Thanks, > ~t~ > > > On Thu, Oct 11, 2012 at 1:26 PM, ceki <c...@qos.ch> wrote: > >> On 11.10.2012 12:43, Mark Struberg wrote: >> >> > ceki, really, this is perfect example why no container uses >> > commons-logging anymore. Do you like to repeat these errors? >> > >> > I reiterate: there is a workaround by isolating this in >> > ClassWorlds. It is not yet there, but ff we like to use slf4j then we >> > will need to implement that. >> >> How about looking at actual plugins? Do you have examples of plugins >> declaring a dependency on slf4j? Anyone else? >> >> >> -- >> Ceki >> 65% of statistics are made up on the spot >> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: > dev-unsubscribe@maven.apache.**org<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
