You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Jarett Millard (JIRA)" <ji...@apache.org> on 2017/07/09 22:08:00 UTC

[jira] [Comment Edited] (CB-12554) More versatile CLI scripts to handle changes in Android SDK Tools 25.3.1

    [ https://issues.apache.org/jira/browse/CB-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079735#comment-16079735 ] 

Jarett Millard edited comment on CB-12554 at 7/9/17 10:07 PM:
--------------------------------------------------------------

I'm running Linux and I already have {{ANDROID_HOME}} set. The issue is in {{get_gradle_wrapper}}: it searches for the Android Studio install directory to find the gradle wrapper template files but the is no way to specify the install directory on Linux.


was (Author: jarett_millard):
I'm running Linux and I already have `ANDROID_HOME` set. The issue is in `get_gradle_wrapper`: it searches for the Android Studio install directory to find the gradle wrapper template files but the is no way to specify the install directory on Linux.

> More versatile CLI scripts to handle changes in Android SDK Tools 25.3.1
> ------------------------------------------------------------------------
>
>                 Key: CB-12554
>                 URL: https://issues.apache.org/jira/browse/CB-12554
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: cordova-android
>            Reporter: Filip Maj
>            Assignee: Filip Maj
>            Priority: Critical
>             Fix For: 6.2.0
>
>
> In the latest Android SDK Tools (v25.3.1), the {{android}} command no longer operates as expected and instead exits with a non-zero status code and provides a message telling folks to use the {{sdkmanager}} and {{avdmanager}} commands.
> Almost all of the various CLI scripts in cordova-android rely, in one capacity or another, on the {{android}} command and its output.
> Let's use this issue to track support for both old SDK Tools and new ones.
> E.g. CB-12546 tracked the failing {{emulator}} command. The [pull request issued for that issue|https://github.com/apache/cordova-android/pull/366] could be one template on how to handle these SDK Tools-related issues: try to use the old {{android}} command, detect if it fails, and if it does, use the newer {{sdkmanager}} and {{avdmanager}} commands to fill the functionality gap.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org