I personally understand it like this: we depend to much on property finding logic in groovy which then makes error messages obscure for core plugin users. We should change the way we code this kind of things so that the error messages are more expressive when stuff isn't found by: - not using dynamic properties so much and ensuring that stuff being referenced is there - using java which will force us to do what's mentioned in the previous point
There is no bashing. It's just pointing out that using this mechanism isn't quite fit for this purpose. On Wed, Jan 15, 2014 at 8:40 AM, Jochen Theodorou <blackd...@gmx.org> wrote: > Am 13.01.2014 21:04, schrieb Luke Daley: > > >> On 13 Jan 2014, at 12:14 pm, Jochen Theodorou <blackd...@gmx.org> wrote: >> >> Luke, >>> >>> would you say this is because of the exception style used for not >>> finding something? >>> >> >> There's nothing really stopping us using a custom error message in a >> getProperty() implementation and perhaps using a custom >> MissingPropertyException, so I don't think so. >> > > but then I must say I don't get this thread. Sure, if you would do this in > Java, you would do this different and then get another message. Probably > you are forced to make one. And if you are forced to make one, you will of > course ensure a better one.... but here you are practically forced too and > blame instead the property runtime finding logic. Sure, no bashing. Still I > kind of don't see the point you are trying to make anymore now. > > bye blackdrag > > > -- > 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 > > >
