[ 
https://issues.apache.org/jira/browse/CB-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Filip Maj resolved CB-12554.
----------------------------
       Resolution: Fixed
    Fix Version/s: 6.2.0

> 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: 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.3.15#6346)

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

Reply via email to