Sorry - I should have added - "unless your facade uses LocationAwareLogger instead of the normal Logger".
Ralph On Sep 10, 2012, at 9:21 AM, Ralph Goers wrote: > > On Sep 10, 2012, at 7:06 AM, Mark Struberg wrote: > >> >>> Absolutely. In light of commit r1380105, the next step is for you >>> (Maven folks) to formulate a policy for swapping out logging >>> back-ends. >> >> Well that is what this is all about. And we have this solution available in >> Maven since 2004. There is already a logging facade which is widely used: >> org.codehaus.plexus.Logger >> >> >> This is used in whole Maven including all plugins which exist. All Maven >> messages get routed through it. I just see no reason for swapping out A1 for >> A2. At least not if A1 is working for years and all the Maven APIs are using >> it. I'm talking about >100 API signatures we would need to change in an >> incompatible way sooner or later! >> >> >> I'm perfectly fine to back the plexus.Logger facade with SLF4J as default >> impl, but please let's not get this into our API or export it to users! > > You shouldn't be fine with this. When you wrap SFL4J with a facade you will > lose all the stack trace info that tells you where your log events are being > generated as they will all point to the facade instead of the actual code > doing the logging. > > Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
