[Android-tools-devel] android gradle plugins setup

Hans-Christoph Steiner hans at at.or.at
Wed Jul 20 07:54:41 UTC 2016


I think we can do it using the same mechanism as gradle's "standard
plugins":
https://docs.gradle.org/current/userguide/standard_plugins.html

Those are the plugins that come with the gradle binary zips.  I imagine
its just a standard path that we can customize with a patch or some
other way.

.hc

Hans-Christoph Steiner:
> 
> What I'd love to see is gradle automatically using the Android gradle
> plugin package without the user having to modify the build.gradle.  But
> that shouldn't happen in a non-standard way.
> 
> Does anyone know if gradle has some concept of "system plugins", i.e.
> plugins that are included as part of the installed base rather than
> something to be downloaded from a maven repo?
> 
> .hc
> 
> Chirayu Desai:
>> Getting #819074 [2] fixed might be a good way to get started. I
>> remember the app picking up the gradle jars which are already
>> installed by using mavenLocal() [3] and /etc/maven/settings-debian.xml
>>
>> [2]: bugs.debian.org/819074
>> [3]: https://gitlab.com/cde/AndroidHelloWorld/blob/debian-test/build.gradle
>>
>> On Wed, Jul 20, 2016 at 2:16 AM, Hans-Christoph Steiner <hans at at.or.at> wrote:
>>>
>>>
>>> One open issue is making gradle find and use the Debian-packaged
>>> versions of the android plugins.  That's mostly a question of figuring
>>> which gradle mechanism would be best used to do this.



More information about the Android-tools-devel mailing list