Maybe a better way to think of this is as a default task/plugin "search path" rather than "applying a plugin". If gradle can find it, then it makes sense to me for gradle to go ahead and try to do what the user asked rather than toss an error.
In many cases I suspect gradle could do useful things in a project without a build.gradle existing at all. Just my $0.02 Philip On Wed, Sep 22, 2010 at 5:10 AM, Tomek Kaczanowski <[email protected]> wrote: > Matthias, > > If I download some open-source project, I would like to be able to type: > gradle NameOfMyIDE > and have a project for my IDE generated without the need of hacking > build.gradle. > > BTW. I don't care about where technically these plugins are located > (gradle-core or whatever) as long as it works the way described above. > > 2010/9/22 Pfau, Matthias <[email protected]>: >> Hi together, >> I do not like the idea of auto-applying built-in plugins because I think >> that there shouldn't be any built-in plugins. I think that all plugins >> should be moved out of the gradle-core. >> >> Kind regards, >> Matthias > > -- > Regards / Pozdrawiam > Tomek Kaczanowski > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
