I'd do it only if it's cheap. My assumption is that the deprecation warning is logged when the property is accessed/written, regardless if the property was configured with a convention mapping or not? If that's the case then the plugin author will have to update the mapping anyway to get rid of the warning triggered when the property is used. (Unless I'm wrong... :)
Cheers! On Thu, Feb 23, 2012 at 11:57 PM, Adam Murdoch <[email protected]>wrote: > Hi, > > I wonder if we should log a deprecation warning when a convention mapping > is set on a deprecated property. The reasoning being that setting a > convention mapping is a 'usage' of the property that will break when the > property is removed. > > Thoughts? > > > -- > Adam Murdoch > Gradle Co-founder > http://www.gradle.org > VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting > http://www.gradleware.com > > -- Szczepan Faber Principal engineer@gradleware Lead@mockito
