Thanks a lot for the definitive answer Jesse. I'm watching the issue.

In the meantime I've indeed switched to Groovy views for at least better
detection of refactored names.

Cheers

2015-10-27 23:01 GMT+01:00 Jesse Glick <[email protected]>:

> On Tue, Oct 27, 2015 at 12:24 PM, Baptiste Mathus <[email protected]> wrote:
> > is this expected? (I mean, calling something absent and that being just
> > ignored)
>
> Yes.
>
> > is there a way to enable an aggressive mode, at least for example in dev
> > mode, that would just throw a stack trace in my face?
>
> No.
>
> JEXL and Jelly were just poor choices for a rendering engine in a big,
> modular application. You can use Groovy views, which will report some
> errors of this kind, though Groovy is a sufficiently complex and
> dynamic language that it will let almost anything past the compiler,
> and a lot of weird stuff past the runtime too.
>
> I filed https://issues.jenkins-ci.org/browse/JENKINS-31203 to track
> some ideas I have been mulling over.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2vZdOVgPb8OuYRrFQDj9JYsLd6aQG5cJOax9dxxPCCmA%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4Os202YqgnYwQv38R1S19XG88%3DJGt9Ls83ZYV8_5JTnA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to