Using a deprecation warning for statement labels in build scripts (which is a bug in 99.9% of the cases) seems overly dogmatic to me. But more importantly, turning errors into deprecations brings along two technical problems that I haven't been able to solve:
1. If we don't fail the build, the build script will be cached. Since the detection is implemented as an org.gradle.groovy.scripts.Transformer, detection will not run again until the build script is edited. To the user, this looks like a sporadic deprecation warning that's coming and going without apparent reason. 2. I can't find a way to determine the name and path of the build script from within the transformer. This information is necessary to produce a good deprecation message. (If we failed the build, this information would be provided automatically.) Whether we should do the same for classes in build scripts is a good question. I think it could be useful but don't have a strong opinion. Cheers, Peter -- View this message in context: http://gradle.1045684.n5.nabble.com/Statement-labels-in-build-scripts-tp5658497p5661795.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
