On Wed, Jul 10, 2013 at 4:30 AM, Cédric Champeau
wrote:
> I must second Jochen here. That getCallerClass doesn't work anymore in
> an update release is unacceptable to me. As Jochen explained, there's no
> suitable replacement so far. We can live with getCallerClass
> disappearing if there's a rep
Am 10.07.2013 10:40, schrieb Noctarius:
[...]
> Maybe a solution could be an annotation to mark calls to not
> appear in any stacktrace?
I had that idea too, and then found it no solution... only I don't
remember why anymore.. Didn't JSR292 include at one time such an annotation?
bye Jochen
--
Am 10.07.2013 10:30, schrieb Cédric Champeau:
> Hi guys,
>
> I must second Jochen here. That getCallerClass doesn't work
> anymore in an update release is unacceptable to me. As Jochen
> explained, there's no suitable replacement so far. We can live
> with getCallerClass disappearing if there's a
Hi guys,
I must second Jochen here. That getCallerClass doesn't work anymore in
an update release is unacceptable to me. As Jochen explained, there's no
suitable replacement so far. We can live with getCallerClass
disappearing if there's a replacement, but obviously, the
@CallerSensitive "solu
