On 27/03/2012, at 3:00 AM, Luke Daley wrote:

> Hi David,
> 
> In the future, please avoid using the list for usage questions. It is used to 
> discuss the development of Gradle itself.
> 
> http://forums.gradle.org is the primary support channel.
> 
> Answers are inline…
> 
> On 26/03/2012, at 3:56 PM, David Resnick wrote:
> 
>> Hi,
>> 
>> I would like to upgrade to m9, but the warnings from a plugin I'm
>> using (gradle-rpm-plugin) due to internal dynamic properties use is
>> making this difficult.
>> 
>> The simplest solution would be to fix the plugin, but how that should
>> be done is not clear to me. The plugin calls
>> AbstractTask.setProperty(...), which is what triggers the warnings. Is
>> there any straightforward replacement to that?
> 
> «thing».ext.set(…)
> 
> However, plugins should NEVER add dynamic/extra properties (they should add 
> extensions).

No. Plugins can use extra properties. They are currently the only way to get 
input from the user via the command-line, for example.

We don't want different mechanisms for build scripts and plugins to achieve the 
same thing. If a feature is available for build scripts to use, it is quite 
fine for plugins to use it. And vice versa.


> 
> 
>> A different alternative would be turning off the dynamic properties
>> use warnings. I would prefer that this is done inside the plugin
>> (leaving warnings regarding dynamic properties use in my gradle
>> scripts to still be emitted), though I could also go with turning of
>> the dynamic properties warnings completely. Is either option
>> supported?
> 
> Unfortunately, neither are right now.
> 
> Your options are to lobby the RPM plugin developer to update the code or to 
> live with the warnings.
> 
> This lack of flexibility in the deprecation warnings is a known issue and 
> will be addressed.
> 
> -- 
> Luke Daley
> Principal Engineer, Gradleware 
> http://gradleware.com
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>    http://xircles.codehaus.org/manage_email
> 
> 


--
Adam Murdoch
Gradle Co-founder
http://www.gradle.org
VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
http://www.gradleware.com

Reply via email to