On Wed, Jul 20, 2011 at 4:35 PM, Adam Murdoch
<[email protected]>wrote:
>
> On 20/07/2011, at 11:03 AM, Eric Berry wrote:
>
> Ah. so would still require each project to define the buildscript in their
> build.gradle file, then I don't think it'll work for my needs.
>
>
> Not necessarily. You would be able to do something like:
>
> buildscript.repositories { ... }
>
> apply plugin: 'plugin', group: 'group', name: 'module', version: 'version'
>
Right, but each project would have to have this snippet in it's build.gradle
file. I suppose I could make a small build script available which does this,
then all developers would just use:
apply from: 'http://url/to/corporate-build.gradle'
That could work, and then there wouldn't need to be any changes to gradle
itself.
The corporate-build.gradle would just setup the buildscript.repositories,
buildscript.dependencies, and then apply my corporate-plugin.
The goal was to have everything setup in a single apply method call, and I
guess this satisfies that.
Cheers,
Eric
--
Learn from the past. Live in the present. Plan for the future.
Blog: http://eric-berry.blogspot.com
jEdit <http://www.jedit.org> - Programmer's Text Editor
Bazaar <http://bazaar.canonical.com> - Version Control for Humans
