I generally use Jelly views by default, but switch to Groovy if the view really needs some complex logic in it: something beyond accessing public properties of Java objects and doing simple if-then tests.
Really I would prefer a different view engine altogether, based on `src/main/java/**/*.java` logic + static prototype `src/main/resources/**/*.html`, but that is a topic for another day… -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3SXxvEJqxTiDYNRWTjtQ9S99DQzMJ%2BisLv33eOvs4iDg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
