This doesn't directly answer your question, but I would highly recommend
switching to using groovy views. It is SOO much easier to debug what is
going wrong compared to Jelly.
On Mon, Mar 9, 2015 at 4:28 PM Thom Ellis wrote:
> Alright, I've been staring at this one for a bit, and I must be m
Alright, I've been staring at this one for a bit, and I must be missing
something obvious, and I'm just not seeing it, so hoping someone can point
out what it is :) I'm just trying to figure out how you get at variable
values that come from a nested class. What I have is a build result action