I agree but sincerely I'm sure that less than 0,01% of our users will
customize their logs.


On Sat, Dec 1, 2012 at 9:27 PM, Anders Hammar <[email protected]> wrote:

> > In any case doing a choice nowadays for 3.1.0 won't prevent us to change
> it
> > in the future. I really hope that the ability to switch from a logger
> > implementation to another won't require several days of developments or I
> > really missed something about it.
> >
>
> Well, very likely it would affect the end users as the logger configuration
> would be different. And that could be confusing and also have people
> convert their adapted logger config files.
>
> /Anders
>
>
> >
> > Cheers
> >
> >
> > Arnaud
> >
> >
> >
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le samedi 1 décembre 2012 09:17:52 Arnaud Héritier a écrit :
> > > > Hi Jason,
> > > >
> > > >   Couldn't we have a look at olamy's log4j2 branch to see if we could
> > > > sanitize / merge it to propose at least one change for the end user
> > > > and demonstrate the interest of the change about logs : a colorized
> > > > console.
> > > >
> > > >   I remember you did that in mvnsh/teslashell a long time ago (as an
> > > > extension ?) and perhaps it could be easy to add properly this
> feature
> > > > in 3.1.0 (otherwise it won't be before a 3.2.0).
> > > >
> > > >   Myself I'm using a 3.1.0 fork with this patch and I' m really
> > > > satisfied (it's so good to quickly see highlighted warning and errors
> > > > ). I merged it back in the last 3.1.0 tag you did without issue
> > > >
> > > >   Wdyt?
> > > >
> > > > ---------
> > > > Arnaud
> > > >
> > > > Le 1 déc. 2012 à 00:20, Jason van Zyl <[email protected]> a écrit :
> > > > > I'm done with the issues that cropped up so I'm ready to re-spin
> > 3.1.0.
> > > > >
> > > > > Anyone want to add anything or discuss anything before I spin this?
> > I'm
> > > > > not in any rush so if folks want to talk about logging we can. But
> > > given
> > > > > the fact once SLF4J initializes it can't change the implementation
> > > > > plugins integrating with Maven need to use the implementation we
> > > choose.
> > > > > This is how everything else in the world that integrates SLF4J has
> to
> > > > > operate so I don't really see us being any different.
> > > > >
> > > > > I'll wait until tomorrow to re-spin.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Jason
> > > > >
> > > > > ----------------------------------------------------------
> > > > > Jason van Zyl
> > > > > Founder & CTO, Sonatype
> > > > > Founder,  Apache Maven
> > > > > http://twitter.com/jvanzyl
> > > > > ---------------------------------------------------------
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [email protected]
> > > > For additional commands, e-mail: [email protected]
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
> >
> >
> > --
> > -----
> > Arnaud Héritier
> > http://aheritier.net
> > Mail/GTalk: aheritier AT gmail DOT com
> > Twitter/Skype : aheritier
> >
>



-- 
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Reply via email to