groovy + spring boot 1.2.0.RELEASE doesn't work with default autoconfiguration

[cfieber]

Threw together a quick example of this:
https://github.com/cfieber/boot-bugs

A vanilla @EnableAutoConfiguation app with groovy in the classpath fails because GroovyTemplateAutoConfiguration activates which fails because there is no templates classpath resource:
https://github.com/cfieber/boot-bugs/blob/master/src/main/groovy/bootbugs/MainBroken.groovy

workaround is to exclude GroovyTemplateAutoConfiguration:
https://github.com/cfieber/boot-bugs/blob/master/src/main/groovy/bootbugs/Main.groovy

[cfieber]

maybe related somewhat to #2184 though in my case I have no templates and am not doing any template rendering, just shipping json from rest controllers

[philwebb]

I think you've hit #1915. It seems like using groovy-all and not wanting templating is going to be more common that accidentally forgetting the /templates folder. I've updated the check so that it's now skipped if groovy-all is being used.

@wilkinsona I think this is a good compromise, probably better than turning off the check all together. Let me know if you think otherwise.

[cfieber]

thanks @philwebb !