On 23/06/2013, at 8:26 PM, kelemen <attila.keleme...@gmail.com> wrote:
> Hi, > > As asked by Luke Daley, I'm sending my notes on lazy configuration to the > dev list. The idea of lazy task confiuration is roughly described here: > http://forums.gradle.org/gradle/topics/allow_tasks_to_be_configured_just_before_execution > > I will summarize: > > As I know, you are already working on lazy configuration. I would like to > have some notes and reguests. > > 1. I believe that my proposed lazy task configuration can solve many > practical problems and is a simple concept: Easy to comprehend. In short, > lazy task configuration is a configuration block which is executed just > before the task is executed. > 2. I understand, that you want something more generic. If I can have a word > on it, I would like if you don't make something like > publications { > // lazy block > } > > This is because making some of the configuration block lazy while others > being eager (they must remain eager until Gradle 2 for backward > compatibilty), is inconsistent and very confusing. So rather, I'd prefer a > syntax like this: > > publications lazy { > // lazy block > } > > This can be extended to other parts of Gradle in the future. There's two main “issues” with this approach. 1. We are trying to avoid you have to tell Gradle when something should happen; which leads into… 2. To do this properly, Gradle really needs to know the nature of the configuration so it can schedule it appropriately A strong goal is to make this work in such a way that a build script author (different to a plugin author) isn't confronted with this issue and it just works. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
