I agree. That doesn't change that log4j2 is young compared to logback and I could understand that people could prefer to select it over log4j for that reason. Myself I have really no preference
The best I suppose will be to open a thread to discuss about pros and cons of each ones and then vote. (For me all of this is probably to much to just select which lines if codes will do our println with colors but I think it will be better for the community to be sure to ear and respect the choice of developers...) --------- Arnaud Le 1 déc. 2012 à 14:00, Olivier Lamy <[email protected]> a écrit : > 2012/12/1 Gary Gregory <[email protected]>: >> Log4j2 supports color consoles, even on Windows. Is this support >> incomplete? I know, I know,still in beta. > sometimes version naming doesn't have a real added value (IMHO) > > some projects use 0.1.x model without any alpha/beta qualifier > some others use beta/alpha qualifier > > so frankly it's a just sometimes a "marketing" choice :-) > Hey we lived here very long with something called > plexus-container-default 1.0-alpha-x and we released a lot of versions > of maven 2.x with that :-) > >> >> Gary >> >> On Dec 1, 2012, at 5:05, Mark Struberg <[email protected]> wrote: >> >>> sounds great, have Oliviers branch running locally myself without issues. >>> >>> LieGrue, >>> strub >>> >>> >>> >>> >>> ----- Original Message ----- >>>> From: Arnaud Héritier <[email protected]> >>>> To: Maven Developers List <[email protected]> >>>> Cc: >>>> Sent: Saturday, December 1, 2012 9:17 AM >>>> Subject: Re: Re-spinning 3.1.0 >>>> >>>> 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] >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > --------------------------------------------------------------------- > 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]
