Re: @Log annotation

An actual JSR would be great, and with the current development pace of Java, I think it could actually be accepted. On Thu, 19 Jul 2018 at 14:35, Rob Tompkins wrote: > > > > On Jul 19, 2018, at 2:35 PM, Ralph Goers > wrote: > > > > It has been brought up before. You can read about the JSR proce

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

Dominik, There are a number of issues in your tracker that are directly related to sticking with NetStandard 1.3. That was an early release and must have been painful to try to do a full implementation of Log4Net. 2 issues dear to me are Variable Expansion (Environment.GetEnvironmentVariable

Re: @Log annotation

> On Jul 19, 2018, at 2:35 PM, Ralph Goers wrote: > > It has been brought up before. You can read about the JSR process at > http://jcp.org . Seems like we’d want to make this a collaborative effort, particularly because they look for a collection of experts. I’ll see if I

Re: @Log annotation

It has been brought up before. You can read about the JSR process at http://jcp.org . Ralph > On Jul 19, 2018, at 11:19 AM, Rob Tompkins wrote: > > That doesn’t seem like a bad idea at all. Have you done that before or are > you at least familiar with the process so that I co

Re: @Log annotation

That doesn’t seem like a bad idea at all. Have you done that before or are you at least familiar with the process so that I could begin working on that? -Rob > On Jul 19, 2018, at 2:04 PM, Ralph Goers wrote: > > We should really propose a new Logging JSR. I would make sure it includes > the

Re: @Log annotation

We should really propose a new Logging JSR. I would make sure it includes the ability for the compiler to provide the class name, method name and line number as “special” variables. Ralph > On Jul 19, 2018, at 10:53 AM, Gary Gregory wrote: > > Maybe the smallest feature we could/should start

Re: @Log annotation

Maybe the smallest feature we could/should start with it a class-level @ClassLogger() annotation which create a static final Logger initialized with the class name. Too bad Java does not have what Smalltalk calls class instance variables. I am using "ClassLogger" like JUnit has ClassRule so it lea

Re: @Log annotation

> On Jul 19, 2018, at 1:41 PM, Ralph Goers wrote: > > To be clear, Log4j-core should have no required dependencies other than > Log4j-API. And we would like to keep optional dependencies to a minimum. Right that makes sense to me. Hence it being an after thought, and I like Gary’s suggestio

Re: @Log annotation

To be clear, Log4j-core should have no required dependencies other than Log4j-API. And we would like to keep optional dependencies to a minimum. Ralph > On Jul 19, 2018, at 10:36 AM, Gary Gregory wrote: > > eOn Thu, Jul 19, 2018 at 10:19 AM Rob Tompkins > wrote: >

Re: @Log annotation

eOn Thu, Jul 19, 2018 at 10:19 AM Rob Tompkins wrote: > > > > On Jul 19, 2018, at 11:48 AM, Gary Gregory > wrote: > > > > FTR: https://projectlombok.org/features/log > > > > On Thu, Jul 19, 2018 at 8:48 AM Gary Gregory > wrote: > > > >> > >> > >> On Thu, Jul 19, 2018 at 8:26 AM Rob Tompkins >

Re: @Log annotation

> On Jul 19, 2018, at 11:48 AM, Gary Gregory wrote: > > FTR: https://projectlombok.org/features/log > > On Thu, Jul 19, 2018 at 8:48 AM Gary Gregory wrote: > >> >> >> On Thu, Jul 19, 2018 at 8:26 AM Rob Tompkins wrote: >> >>> >>> On Jul 19, 2018, at 10:17 AM, Gary Gregory >>> wr

Re: @Log annotation

FTR: https://projectlombok.org/features/log On Thu, Jul 19, 2018 at 8:48 AM Gary Gregory wrote: > > > On Thu, Jul 19, 2018 at 8:26 AM Rob Tompkins wrote: > >> >> >> > On Jul 19, 2018, at 10:17 AM, Gary Gregory >> wrote: >> > >> > On Thu, Jul 19, 2018 at 8:07 AM Rob Tompkins >> wrote: >> > >>

Re: @Log annotation

On Thu, Jul 19, 2018 at 8:26 AM Rob Tompkins wrote: > > > > On Jul 19, 2018, at 10:17 AM, Gary Gregory > wrote: > > > > On Thu, Jul 19, 2018 at 8:07 AM Rob Tompkins wrote: > > > >> > >> > >>> On Jul 19, 2018, at 9:29 AM, Gary Gregory > >> wrote: > >>> > >>> Annotation-based logging comes up on

Re: @Log annotation

Would this work via code generation, bytecode weaving (compile time or as a Java agent at runtime), reflection, or some other mechanism I’m not thinking of? Lombok goes further and modifies the AST at compile time as if Java supported macros, so that’s not the most straightforward route of implemen

Re: @Log annotation

> On Jul 19, 2018, at 10:17 AM, Gary Gregory wrote: > > On Thu, Jul 19, 2018 at 8:07 AM Rob Tompkins wrote: > >> >> >>> On Jul 19, 2018, at 9:29 AM, Gary Gregory >> wrote: >>> >>> Annotation-based logging comes up once in a while here but we have not >>> implemented it. Project Lombok do

Re: @Log annotation

On Thu, Jul 19, 2018 at 8:07 AM Rob Tompkins wrote: > > > > On Jul 19, 2018, at 9:29 AM, Gary Gregory > wrote: > > > > Annotation-based logging comes up once in a while here but we have not > > implemented it. Project Lombok does that IIRC. > > Any reason for having not yet implemented it, or ju

Re: @Log annotation

> On Jul 19, 2018, at 9:29 AM, Gary Gregory wrote: > > Annotation-based logging comes up once in a while here but we have not > implemented it. Project Lombok does that IIRC. Any reason for having not yet implemented it, or just the standard “time”? > > Gary > > On Thu, Jul 19, 2018, 07:15

Re: @Log annotation

Annotation-based logging comes up once in a while here but we have not implemented it. Project Lombok does that IIRC. Gary On Thu, Jul 19, 2018, 07:15 Rob Tompkins wrote: > Hey folks, > > I’m curious if anyone has thought about adding a class level @Log > annotation such that upon debug or trac

@Log annotation

Hey folks, I’m curious if anyone has thought about adding a class level @Log annotation such that upon debug or trace configuration, method entry and exit gets automatically logged? -Rob