Luke,
would you say this is because of the exception style used for not
finding something?
Am 11.01.2014 14:51, schrieb Luke Daley:
Hi,
I don't mean to be inflammatory by my subject. This is not an attack on Groovy.
I just tried to upgrade a project to Gradle 1.10 and was greeted with this
error: “Could not find property 'ideaProject' on task set.”
Tracked it down to this:
https://github.com/gradle/gradle/blob/master/subprojects/ide/src/main/groovy/org/gradle/plugins/ide/idea/IdeaPlugin.groovy#L177
“project.rootProject.tasks.ideaProject” will produce this error the IDEA plugin
isn't applied to the root.
Because of our many layers of dynamic indirection, the error messages when
using DSL style Groovy in infrastructure can be not very clear. This isn't
Groovy's fault. It's that using Groovy in our infrastructure makes it tempting
to go the shortest (untyped) path and this is susceptible to obtuse error
messages and bad user experiences. If we'd used Java in _this_ particular
instance we'd have had a better error message.
Granted that we should also strive to make the error messages better for DSL
users so there's a balance here of course. For core infrastructure though, I'm
for us taking on the pain of writing in Java if it helps the user through
better error reporting.
--
Jochen "blackdrag" Theodorou - Groovy Project Tech Lead
blog: http://blackdragsview.blogspot.com/
german groovy discussion newsgroup: de.comp.lang.misc
For Groovy programming sources visit http://groovy-lang.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
