Great news Howard,
I'll try the fix right away. Thanks for your awesome work!
--
Olaf Tomczak
2012/4/13 Steve Eynon
> Oh sweet. That is good news, cheers!
> --
> Steve Eynon
> ---
> "If at first you don't succeed,
>so much for skydiving!"
>
>
>
>
> On 13 April 2
Oh sweet. That is good news, cheers!
--
Steve Eynon
---
"If at first you don't succeed,
so much for skydiving!"
On 13 April 2012 06:47, Howard Lewis Ship wrote:
> Turns out its mutable fields that don't work. I was fooled because my
> tests mistakenly only attem
Turns out its mutable fields that don't work. I was fooled because my
tests mistakenly only attempted injected fields.
In any case, it is fixed in 5.3.3-rc-3.
On Wed, Apr 11, 2012 at 9:20 PM, Steve Eynon
wrote:
> Hello,
>
> Directly accessing instrumented fields (@Parameter etc...) from
> subcl
Hello,
Directly accessing instrumented fields (@Parameter etc...) from
subclasses does not work. This is fine, but I do wish T5 complained
bitterly when it finds a instrumented field marked as non-public.
Olaf found similar problems here (TAP5-1860):
http://tapestry.1045711.n5.nabble.com/Protecte
