On Sep 25, 2012, at 8:36 AM, Noel Grandin wrote:
>
> On 2012-09-25 04:50, Gary Gregory wrote:
>> For SC, since you are recompiling, IMO, it is OK for a MAJOR release to be
>> different and print the stack trace.
>>
>> It is just so nice to say debug(Throwable) and have the right thing (IMO
>>
On Sep 25, 2012, at 8:42 AM, Gary Gregory wrote:
> On Tue, Sep 25, 2012 at 11:03 AM, Ralph Goers
> wrote:
> Can you look at the context of where you like to write
> logger.error(Throwable) and see if it is at all possible to do something with
> annotations there? For example, in a catch stat
On Tue, Sep 25, 2012 at 11:03 AM, Ralph Goers wrote:
> Can you look at the context of where you like to write
> logger.error(Throwable) and see if it is at all possible to do something
> with annotations there? For example, in a catch statement could you do
>
> catch (@log UnsupportedOperationEx
On 2012-09-25 04:50, Gary Gregory wrote:
For SC, since you are recompiling, IMO, it is OK for a MAJOR release
to be different and print the stack trace.
It is just so nice to say debug(Throwable) and have the right thing
(IMO again) happen.
Having code say debug(throwable.toString(), throwa
Can you look at the context of where you like to write logger.error(Throwable)
and see if it is at all possible to do something with annotations there? For
example, in a catch statement could you do
catch (@log UnsupportedOperationException ex)
This kind of use of annotations is something I'v
The issue is closed so I'll comment here.
Over all, my port to 2.0 went well, aside from some 1.2 compat issue I
JIRA'd.
Let's make a difference between binary compat and source compat. BC is no
problem, calling error(), info(), and so on with a Throwable is the same as
with 1.2.
For SC, since y
