> On Jul 19, 2018, at 10:17 AM, Gary Gregory <garydgreg...@gmail.com> wrote:
>
> On Thu, Jul 19, 2018 at 8:07 AM Rob Tompkins <chtom...@gmail.com> wrote:
>
>>
>>
>>> On Jul 19, 2018, at 9:29 AM, Gary Gregory <garydgreg...@gmail.com>
>> 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”?
>>
>
> It's just more "stuff" and yes, time. And also, no one's wanted to put the
> time in.
>
> But then there are design issues and adding more "stuff" to the API jar.
>
> - Would you allow @Log(level=Level.TRACE) (should be the default?) and
> @Log(level=Level.DEBUG)
> - What happens if you say both?
> - Should you be able to break it up and only say @LogEntry() or @LogExit().
> - What about @Log(file="${user.home}\foo.log")
> - and on and on ;-)
Definitely fair points, I think I would try to go as simple as possible in a
first pass…right?
@Log
@Log(level=X)
-Rob
>
> Gary
>
>
>>
>>>
>>> Gary
>>>
>>> On Thu, Jul 19, 2018, 07:15 Rob Tompkins <chtom...@gmail.com> wrote:
>>>
>>>> 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
>>
>>
