Re: Log4j Warning

2016-01-09 Thread Jason van Zyl
t;>> in >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>> >>&

Re: Log4j Warning

2016-01-09 Thread Tamás Cservenák
apache.logging.slf4j.Log4jLoggerFactory > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> If I asked Ceki for help I’d get it immediately also. Who > &

Re: Log4j Warning

2016-01-09 Thread Jason van Zyl
;>>>>>>>>>> any >>>>>>>>>>>>>>>> choice they are doing it doesn't avoid you to use another >>> one >>>> in >>>>>>>>> your >>>>>>>>>>>>> own >&

Re: Log4j Warning

2016-01-08 Thread Tamás Cservenák
>>>>>>>> examination, issue submissions, pull requests and ultimately >> > more >> > >>>>> people >> > >>>>>>>>>>> that contribute and that’s clearly the case with Logback. I >> > don’t >&g

Re: Log4j Warning

2016-01-08 Thread Jason van Zyl
> On Jan 8, 2016, at 3:21 PM, Dennis Lundberg wrote: > > Hi, > > The sometimes heated discussion in this thread shows that there are strong > opinions about logging implementation. That for me is a reason to not > bundle one by default. > > Let us focus on making it as simple as possible for o

Re: Log4j Warning

2016-01-08 Thread Jason van Zyl
You’re welcome. I do try to bring a chuckle to everyone’s day. > On Jan 8, 2016, at 3:48 PM, Gary Gregory wrote: > > On Fri, Jan 8, 2016 at 4:12 AM, Jason van Zyl wrote: > >> >>> On Jan 7, 2016, at 9:17 PM, Gary Gregory wrote: >>> >>> On Thu, Jan 7, 2016 at 7:26 AM, Jason van Zyl wrote: >>

Re: Log4j Warning

2016-01-08 Thread Gary Gregory
On Fri, Jan 8, 2016 at 4:12 AM, Jason van Zyl wrote: > > > On Jan 7, 2016, at 9:17 PM, Gary Gregory wrote: > > > > On Thu, Jan 7, 2016 at 7:26 AM, Jason van Zyl wrote: > > > >> No, I don’t that useful. If it’s an extensions then it can be activated > >> using the .mvn/extensions.xml and downloa

Re: Log4j Warning

2016-01-08 Thread Dennis Lundberg
Hi, The sometimes heated discussion in this thread shows that there are strong opinions about logging implementation. That for me is a reason to not bundle one by default. Let us focus on making it as simple as possible for our end users to configure which one they want to use. I'm not familiar

Re: Log4j Warning

2016-01-08 Thread Ralph Goers
On traction we can agree to disagree. Logback may be more popular but we are pretty busy answering user's questions, and making enhancements and fixes. I follow the Logback lists and actually see less activity there. And I continue to see users ask frameworks to support Log4j 2. Frankly, I was s

Re: Log4j Warning

2016-01-08 Thread Jason van Zyl
Ralph, The simple fact of the matter is that Log4J2 appears to have little to no user traction at all. This suggests to me that the community forked into the next generation by way of Logback and Log4J2. The community appears to have gone in the direction of Logback. By a very large margin, at

Re: Log4j Warning

2016-01-08 Thread Jason van Zyl
> On Jan 7, 2016, at 9:17 PM, Gary Gregory wrote: > > On Thu, Jan 7, 2016 at 7:26 AM, Jason van Zyl wrote: > >> No, I don’t that useful. If it’s an extensions then it can be activated >> using the .mvn/extensions.xml and downloaded on demand. I think for Maven >> 4.x we just bite the bullet an

Re: Log4j Warning

2016-01-08 Thread Tamás Cservenák
t;>>>> > > >>>>>>>>>>>> > > >>>>>>>>>>>> > > >>>>>>>>>>>> On Wed, Jan 6, 2016 at 5:46 PM, Jason van Zyl < > > ja...@takari.io> > > >>>>> wrote: > > >>>>>>>>

Re: Log4j Warning

2016-01-07 Thread Gary Gregory
t;> ==>62389 > >>>>>>>>>>>>> > >>>>>>>>>>>>> gremlin> g.V('vc', > >>>>> 'org.apache.logging.log4j:log4j-core').inE.count() > >>>>>>>>>>>>> ==>31

Re: Log4j Warning

2016-01-07 Thread Gary Gregory
py Holidays. > >>>>>>>>>> > >>>>>>>>>> Can the next version of Maven be rid of this warning: > >>>>>>>>>> > >>>>>>>>>> [WARN] The SLF4J binding actually used is n

Re: Log4j Warning

2016-01-07 Thread Gary Gregory
On Thu, Jan 7, 2016 at 9:56 AM, Jason van Zyl wrote: > > > On Jan 7, 2016, at 11:43 AM, Arnaud Héritier > wrote: > > > > No problem. > > Let's do what you want (like always). > > Not that I want it, but that’s certainly never been the case. The project > would most definitely look different if i

Re: Log4j Warning

2016-01-07 Thread Ralph Goers
I apologize for this email. It was not meant for this list. Ralph > On Jan 7, 2016, at 11:47 AM, Ralph Goers wrote: > > He claims that Log4j 2 isn’t popular enough. The real reason, as you > probably know, is that Jason seriously dislikes me, although he would never > actually say that as hi

Re: Log4j Warning

2016-01-07 Thread Ralph Goers
He claims that Log4j 2 isn’t popular enough. The real reason, as you probably know, is that Jason seriously dislikes me, although he would never actually say that as his reason. Ralph > On Jan 7, 2016, at 10:56 AM, Jason van Zyl wrote: > > >> On Jan 7, 2016, at 11:43 AM, Arnaud Héritier wr

Re: Log4j Warning

2016-01-07 Thread Arnaud Héritier
>>> ==>62389 > >>>>>>>>>>>>> > >>>>>>>>>>>>> gremlin> g.V('vc', > >>>>> 'org.apache.logging.log4j:log4j-core').inE.count() > >>>>>>>>>>

Re: Log4j Warning

2016-01-07 Thread Jason van Zyl
; wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> As we said previously when the the question arose again there >>>>> would >>>>>>>>> be >>>>>>>>>>> a >>>>>>>>>>>>> discussion. You may not remember, b

Re: Log4j Warning

2016-01-07 Thread Igor Fedorenko
but I expect there to be a > > >>>>>>> discussion. > > >>>>>>>>>>>> > > >>>>>>>>>>>> I have built a graph of Maven Central to analyze the rank > > (count > > >>> of > > >>>>>

Re: Log4j Warning

2016-01-07 Thread Arnaud Héritier
t;>>>>>>>> and not the owner project in pretty much the exact same way > users > >>> went > >>>>>>>>> with > >>>>>>>>>>> Jenkins and not Hudson. Anyone is happy to take the graph and > >>> veri

Re: Log4j Warning

2016-01-07 Thread Arnaud Héritier
at 5:46 PM, Jason van Zyl < >> > > ja...@takari.io> >> > > >> > wrote: >> > > >> > >>>>>>> >> > > >> > >>>>>>>> These are the n

Re: Log4j Warning

2016-01-07 Thread Arnaud Héritier
; 'org.apache.logging.log4j:log4j-core').inE.count() > > > >> > >>>>>>>> ==>3134 > > > >> > >>>>>>>> > > > >> > >>>>>>>> These are incoming edges across all versions of said > >

Re: Log4j Warning

2016-01-07 Thread Nick Stolwijk
t; >>>> discussion. > > >> > >>>>>>>>> > > >> > >>>>>>>>> I have built a graph of Maven Central to analyze the rank > > >> (count > > >> > of > > >> > >>>> all > > >&g

Re: Log4j Warning

2016-01-07 Thread Arnaud Héritier
;>> project > >> > >>>>>>>> and not the owner project in pretty much the exact same way > >> users > >> > went > >> > >>>>>> with > >> > >>>>>>>> Jenkins and not Hudson. An

Re: Log4j Warning

2016-01-07 Thread Nick Stolwijk
ed on Logback that I would really like to use, and >> the >> > color >> > >>>>>>>> logging is also easy with Logback. I do not want to use >> something >> > that >> > >>>>>> the >> > >&

Re: Log4j Warning

2016-01-07 Thread Arnaud Héritier
> >>>>>>>> community at large has not adopted. > > > >>>>>>>>> > > > >>>>>>>>> Again, anyone is welcome to the code and/or the data if they > > > want to > > > >>>>&

Re: Log4j Warning

2016-01-07 Thread Arnaud Héritier
t;>>>>> much > > >>>>>>>> here in these discussions but I’m vehemently opposed to > > integrating > > >>>>>> Log4J2. > > >>>>>>>>> > > >>>>>>>>>> On Jan 6, 2016, at 7

Re: Log4j Warning

2016-01-06 Thread Igor Fedorenko
;>> On Jan 6, 2016, at 7:55 AM, Arnaud Héritier < > > aherit...@gmail.com> > > >>>>>>>> wrote: > > >>>>>>>>>> > > >>>>>>>>>> thanks for this valuable comment Jason :( > > &g

Re: Log4j Warning

2016-01-06 Thread Nick Stolwijk
t;>>>> Do not merge this branch. > >>>>>>>>>>> > >>>>>>>>>>>> On Jan 6, 2016, at 4:05 AM, Tibor Digana < > tibordig...@apache.org> > >>>>>>>> wrote: > >>>>>>

Re: Log4j Warning

2016-01-06 Thread Jason van Zyl
t;>>>>>> >>>>>>>>>>>>> Just because only 2.4 was available when I updated this feature >>>>>>>> branch >>>>>>>>>>> few >>>>>>>>>>>>> months ag

Re: Log4j Warning

2016-01-06 Thread Ralph Goers
t;>>>>>>>>> >>>>>>>>>>>>> Thank you for the update. >>>>>>>>>>>>> >>>>>>>>>>>>> Why not update the Log4j 2 dep from 2.4 to 2.

Re: Log4j Warning

2016-01-06 Thread Arnaud Héritier
> > > > > >>>>> - ch.qos.logback.classic.LoggerContext > > > > > >>>>> - org.slf4j.helpers.Log4jLoggerFactory > > > > > >>>>> - org.slf4j.impl.SimpleLoggerFactory > > > > > >>>>> > &g

Re: Log4j Warning

2016-01-06 Thread Olivier Lamy
4jLoggerFactory > > > > >>>>> - org.slf4j.impl.SimpleLoggerFactory > > > > >>>>> > > > > >>>>> Is there a step I am missing to use Log4j 2 cleanly? My steps > are > > > > >> here: > > > &

Re: Log4j Warning

2016-01-06 Thread Arnaud Héritier
gt;>>>> E-Mail: [hidden email] > > > >> <http:///user/SendEmail.jtp?type=node&node=5857870&i=3> > > > > > | [hidden > > > >> email] <http:///user/SendEmail.jtp?type=node&node=5857870&i=4> >

Re: Log4j Warning

2016-01-06 Thread Olivier Lamy
t; | [hidden > > >> email] <http:///user/SendEmail.jtp?type=node&node=5857870&i=4> > > >>> > > >>>>> Java Persistence with Hibernate, Second Edition > > >>>>> <http://www.manning.com/bauer3/> > > >>>>> JUnit in Action,

Re: Log4j Warning

2016-01-06 Thread Jason van Zyl
ser/SendEmail.jtp?type=node&node=5857870&i=0>> a >>> écrit : >>>>>>>>>>>> >>>>>>>>>>>>> Hi Arnaud, >>>>>>>>>>>>> >>>>>>>>>>&g

Re: Log4j Warning

2016-01-06 Thread Jason van Zyl
6 at 2:46 PM, Arnaud Héritier <[hidden email] >>>>>>>>>>> <http:///user/SendEmail.jtp?type=node&node=5857870&i=1> >>>>>>>>>>>> > wrote: >>>>>>>>>>>> >>>>>&g

Re: Log4j Warning

2016-01-06 Thread Paul Benedict
;>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>> > >>>> > >> > maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties > >>>&g

Re: Log4j Warning

2016-01-06 Thread Jason van Zyl
update I did after my old blog post : >>>>>>>>>>> http://www.aheritier.net/united-colors-of-maven/ >>>>>>>>>>> >>>>>>>>>>> BR >>>>>>>>>>> >>>>>>

Re: Log4j Warning

2016-01-06 Thread Paul Benedict
t;>> wrote: > >>>>>>>>> > >>>>>>>>>> Hi All, > >>>>>>>>>> > >>>>>>>>>> Happy Holidays. > >>>>>>>>>> > >>>>>>>>>>

Re: Log4j Warning

2016-01-06 Thread Jason van Zyl
g.slf4j.Log4jLoggerFactory >>>>>>>>>> [WARN] Maven supported bindings are: >>>>>>>>>> [WARN] (from >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>

Re: Log4j Warning

2016-01-06 Thread Michael Osipov
rdpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory -- ----- Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- If you reply to this email, your message will be added to the discussio

Re: Log4j Warning

2016-01-06 Thread Michael Osipov
p://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- If you reply to this email, your message will be a

Re: Log4j Warning

2016-01-06 Thread Arnaud Héritier
ar!/META-INF/maven/slf4j-configuration.properties) > >>>>> > >>>>>>>> - ch.qos.logback.classic.LoggerContext > >>>>>>>> - org.slf4j.helpers.Log4jLoggerFactory > >>>>>>>> - org.slf4j.impl.SimpleLogg

Re: Log4j Warning

2016-01-06 Thread Jason van Zyl
gt;>>>>>> Is there a step I am missing to use Log4j 2 cleanly? My steps are >>>>> here: >>>>>>>> https://garygregory.wordpress.com/2015/03/23/watch-maven-in-color/ >>>>>>>> >>>>>>>> -- >>>>>>>> E-Mail

Re: Log4j Warning

2016-01-06 Thread Jason van Zyl
mail.jtp?type=node&node=5857870&i=4> >>>>> >>>>>>> Java Persistence with Hibernate, Second Edition >>>>>>> <http://www.manning.com/bauer3/> >>>>>>> JUnit in Action, Second Edition <http://www.mann

Re: Log4j Warning

2016-01-06 Thread Tibor Digana
gt;> <http:///user/SendEmail.jtp?type=node&node=5857870&i=3> > > > | [hidden > > >> email] <http:///user/SendEmail.jtp?type=node&node=5857870&i=4> > > >>> > > >>>>> Java Persistence with Hibernate, Second Edi

Re: Log4j Warning

2016-01-06 Thread Arnaud Héritier
>> <http://www.manning.com/bauer3/> > >>>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > >>>>> Spring Batch in Action <http://www.manning.com/templier/> > >>>>> Blog: http://garygregory.wordpress.com > >>>

Re: Log4j Warning

2016-01-06 Thread Jason van Zyl
nning.com/templier/> >>>>> Blog: http://garygregory.wordpress.com >>>>> Home: http://garygregory.com/ >>>>> Tweet! http://twitter.com/GaryGregory >>>>> >>>> >>>> >>>> >>>> -- >>>> - >>>> Arnaud

Re: Log4j Warning

2016-01-06 Thread Arnaud Héritier
witter.com/GaryGregory > > > > > > > > > > > > > > > > > > > > > -- > > > > - > > > > Arnaud Héritier > > > > http://aheritier.net > > > > Mail/GTalk: aheritier AT gmail DOT com >

Re: Log4j Warning

2016-01-06 Thread Tibor Digana
er.net > > > Mail/GTalk: aheritier AT gmail DOT com > > > Twitter/Skype : aheritier > > > > > > > > > > > -- > > E-Mail: [hidden email] > <http:///user/SendEmail.jtp?type=node&node=5857870&i=5> | > [hidden > email] <htt

Re: Log4j Warning

2016-01-04 Thread Arnaud Héritier
Just because only 2.4 was available when I updated this feature branch few months ago. Le mardi 5 janvier 2016, Gary Gregory a écrit : > Hi Arnaud, > > Thank you for the update. > > Why not update the Log4j 2 dep from 2.4 to 2.5? > > Gary > > On Mon, Jan 4, 2016 at 2:46 PM, Arnaud Héritier > wr

Re: Log4j Warning

2016-01-04 Thread Gary Gregory
Hi Arnaud, Thank you for the update. Why not update the Log4j 2 dep from 2.4 to 2.5? Gary On Mon, Jan 4, 2016 at 2:46 PM, Arnaud Héritier wrote: > Hi Gary, > > I fixed this in the branch : > https://github.com/apache/maven/commits/slf4j-log4j2.4 > The fix is in > > maven-embedder/src/main

Re: Log4j Warning

2016-01-04 Thread Arnaud Héritier
Hi Gary, I fixed this in the branch : https://github.com/apache/maven/commits/slf4j-log4j2.4 The fix is in maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties ( https://github.com/apache/maven/commit/8cddea291c279130d437bcdf3337f16296558530 ) It is the update I di

Re: Log4j Warning

2015-12-25 Thread Michael Osipov
Am 2015-12-25 um 16:09 schrieb Gary Gregory: Hi All, Happy Holidays. Can the next version of Maven be rid of this warning: [WARN] The SLF4J binding actually used is not supported by Maven: org.apache.logging.slf4j.Log4jLoggerFactory [WARN] Maven supported bindings are: [WARN] (from jar:file:/E

Log4j Warning

2015-12-25 Thread Gary Gregory
Hi All, Happy Holidays. Can the next version of Maven be rid of this warning: [WARN] The SLF4J binding actually used is not supported by Maven: org.apache.logging.slf4j.Log4jLoggerFactory [WARN] Maven supported bindings are: [WARN] (from jar:file:/E:/Java/apache-maven-3.3.9/bin/../lib/maven-embe