Gretar Arnason wrote:
>
> I don't want to ask everyone to have a buildscript { ... } clause in the
> scripts to download the plugin (which would be duplicated in 30-40
> places).
>
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.
Gretar Arnason wrote:
>
> If there is some other simpler way I can limit the logging I'd appreciate
> a pointer.
>
I already showed a simpler way in my last post. No need for a separate task
and build listener.
--
Peter Niederwieser
Developer, Gradle
http://www.gradle.org
Trainer & Consultant, Gradle Inc.
http://www.gradle.biz
Creator, Spock Framework
http://spockframework.org
--
View this message in context:
http://gradle.1045684.n5.nabble.com/plugin-initialization-in-a-multiproject-build-tp3384288p3384778.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
