On Dec 1, 2012, at 1:44 PM, Olivier Lamy <[email protected]> wrote:
>>
>> I don't think that's particularly easy and additionally opens us up to
>> having to specifically support any SLF4J implementation which I don't think
>> is wise.
>>
> if documented that's not really complicated.
>
So the process would be:
- downloads the new implementation
- change the configuration
- use a command line parameter
> this could be nice for ci servers to get logs easily.
A single good implementation would also work.
> We already have eventspy to intercept build informations so why not
> having something else for logs.
The mechanism for the event spy is just putting an extension on the classpath.
If you wanted to leverage the existing mechanism you can just put the JARs in
the ${MAVEN_HOME}/lib/ext directory along with making your configuration
available, but you're going to have to remove the other SLF4J implementation or
you're going to get the duplicate binding exception. Not a huge deal.
So you can already add a new implementation of SLF4J right now using the
mechanism that exists without anything additional. No modification of the
classwords configuration or a command line parameters which gives it parity
with the event spy if that's what you're looking for.
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
A man enjoys his work when he understands the whole and when he
is responsible for the quality of the whole
-- Christopher Alexander, A Pattern Language
