>From the little I've worked with macros (worked more with scalameta and
shapeless), that looks good so far. If you can add some unit tests, then
we'd be happy to merge!
On 11 December 2017 at 20:41, Jeffrey Shaw wrote:
> Great news! I'm able to run LoggingApp in the scala api repo without it
>
Great news! I'm able to run LoggingApp in the scala api repo without it
calling StackLocatorUtil.calcLocation, but it prints the same messages as
before. I have to use my patch to log4j of course.
See https://github.com/shawjef3/logging-log4j-scala/commits/message-location
On Sun, Dec 10, 2017 at
Hi,
Sorry for being late for the party (I was just checking if there is a
new release for liblog4cxx, which I would really apprecicate when I
came about this thread)
Robert Middleton wrote on Tue, 25 Jul 2017 19:11:09 -0700:
> It's more of an expected behavior - when people download an autotool
Hi Borja,
please ask future questions on one of the official mailing lists, as
documented here:
https://logging.apache.org/log4net/mail-lists.html
As for your question, there is ongoing work to support netstandard-2.0 as a
target along with automating the build process. While implementing these
Not at the moment.
On 2017-12-11 20:02, Ralph Goers wrote:
It will be 2.10.1 unless we have new features to add that warrant a minor
version bump. Do you have new features to add?
Ralph
On Dec 11, 2017, at 11:54 AM, Mikael Ståldal wrote:
Do we plan to do a 2.10.1, or will next release b
It will be 2.10.1 unless we have new features to add that warrant a minor
version bump. Do you have new features to add?
Ralph
> On Dec 11, 2017, at 11:54 AM, Mikael Ståldal wrote:
>
> Do we plan to do a 2.10.1, or will next release be 2.11.0?
>
Do we plan to do a 2.10.1, or will next release be 2.11.0?
