Thanks Peter, appreciate your answers.
On Mon, Feb 14, 2011 at 5:14 PM, Peter Niederwieser <[email protected]>wrote:
>
> Depending on your needs, you could also use "apply from: ...".
>
> Dependencies added to the buildscript {} section of the root project are
> also available in subprojects. (This is subject to change, but we will keep
> use cases like yours in mind.) Adding one buildscript section per project
> is
> definitely better than repeatedly asking everyone to download the Jar
> manually.
>
> I'll reflect on adding the buildscript section to include the plugin,
however I'm hiccuping a little on this duplicated section all over the
place.
Also, maybe to explain my reluctancy, one of the results I really like
by using gradle is how concise the buildscripts can be kept by using
plugins.
That is 'housekeeping' stuff can be kept to a miminum in build files, which
is why I don't want the 'noise' of the plugin housekeeping creeping into the
buildscripts, if you know what I mean.
I'll examine how much noise it will really make though before becoming to
vocal on it though.
I'm also going to look into using the wrapper for building, and I'm guessing
I wouldn't have much option there.
And yes, I agree, asking everyone to download the Jar/plugin manually is
unacceptable as a long term strategy, I really must find some solution to
this, thanks for the help.
Gretar
