On 26/03/2012, at 11:41 PM, Adam Murdoch wrote: > > 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.
Fair point on the command line input. > 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. I'm not convinced here. We can obviously never stop plugin authors from doing this, but I feel pretty strongly that we should encourage plugin authors (of plugins that are publicly distributed) to not do this and to use extensions instead. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com
