Publish Android SDK dependencies to Bintray, with EULA

Artem Zinnatullin

unread,

Jun 27, 2016, 8:01:55 PM6/27/16

to adt-dev

Thousands of Android developers have to deal with Android SDK Manager (2 UIs and 1 old terminal interface) to download dependencies locally and (most problematic) on CI/etc. We've asked you several times why not publish such dependencies to mavenCentral or jCenter, you said that it's because you have EULA that we need to accept before downloading.

Today I was talking to Baruch Sadogursky from JFrog and he said that Bintray recently added support for uploading products with EULA!

User will need to log into Bintray and accept EULA before downloading, then he/she can specify credentials for accessing Bintray in Gradle/Maven and download dependencies like a normal person! You can update EULA and have different versions of it for different versions of products.

Can you please consider Bintray as a hosting for Android SDK artifacts with EULA? Please…

Links:

Tomáš Procházka

unread,

Jun 28, 2016, 4:31:42 PM6/28/16

to adt-dev

It would be great, update SDK on CI server because of new support library or play services is pain.

And after several yer it will download GBs of data to keep all versions of these libraries in the SDK manager, because it always download all version again and again.

Michal Bendowski

unread,

Jun 29, 2016, 6:12:09 AM6/29/16

to adt-dev, Ioana Radu

You may be interested in checking out the new "auto-download" feature in our Gradle plugin 2.2: it will download missing SDK components required for the build, assuming you copy the accepted license files from $ANDROID_HOME to the CI server. Only works from the command line for now.

Michal

Tomáš Procházka

unread,

Jun 30, 2016, 6:38:32 AM6/30/16

to adt-dev, ioa...@google.com

I didn't know about it. Is enough log via SSH to CI a make first update manually with accept licences?

Dne středa 29. června 2016 12:12:09 UTC+2 Michal Bendowski napsal(a):

Artem Zinnatullin

unread,

Jun 30, 2016, 8:34:59 AM6/30/16

to adt-dev

I'll definitely try built-in feature, but don't you feel like it's reinventing the wheel?

How smart will that auto downloading will be and what parts of build dependencies will it download?

Michal Bendowski

unread,

Jul 1, 2016, 5:58:29 AM7/1/16

to adt...@googlegroups.com, Ioana Radu

You need to copy (applicable) $ANDROID_HOME/license/* files to the CI server and that should be enough. Gradle should be able to download the required platform and build tools as well as update extras/google, extras/android repositories and install packages in the new extras/m2repository format (with CMake and NDK on the way). Please file bugs at b.android.com if this doesn't work for you :)

HTH,

Michal

PS. The feature is disabled when Gradle is invoked from AS, since the GUI provides a interactive better experience.

On Thu, Jun 30, 2016 at 1:35 PM Artem Zinnatullin <artem.zi...@gmail.com> wrote:

I'll definitely try built-in feature, but don't you feel like it's reinventing the wheel?

How smart will that auto downloading will be and what parts of build dependencies will it download?

--
You received this message because you are subscribed to a topic in the Google Groups "adt-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adt-dev/_6YNTRFpj3g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adt-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all

Reply to author

Forward