By packaging up the android plugin for Debian, we are in effect making
it "built-in". gradle will never need to download that plugin version
when the package is installed.
All built-in plugins are included in the Gradle project, it does not
need to download the plugins when using.
But one still needs to download custom plugins. Before
gradle-debian-helper, packages in Debian also needs to specify the
local Maven repo URL.
I think it would be a bad idea to
What are the rules for the plugins that are included when you download
the gradle-2.14-bin.zip from gradle.org? Do you have to add a path to
build.gradle to use those files as the plugin binaries? Will gradle try
downloading those from a maven repo? I mean like the Java plugin. I
think in
I have updated the package to 2.0.0 and also tweaked it a little bit:
1. Install Maven artifacts into /usr/share/maven-repo
2. Auto-generate POMs using Gradle
Thus, by adding Debian's maven-repo into the build scripts and change
the Android plugin's classpath version to either "2.0.0" or
Am 23.03.2016 um 14:57 schrieb Hans-Christoph Steiner:
>
> Package: android-platform-tools-base
> Version: 1.5.0-1
> Severity: wishlist
>
> This package includes a couple of gradle plugins, i.e. the Android
> gradle plugins. This package, a new package, or maybe even the
> android-sdk package,
Package: android-platform-tools-base
Version: 1.5.0-1
Severity: wishlist
This package includes a couple of gradle plugins, i.e. the Android
gradle plugins. This package, a new package, or maybe even the
android-sdk package, should have the proper setup so that gradle can
automatically find
6 matches
Mail list logo
