You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/06/14 01:48:20 UTC

[jira] [Commented] (CB-3627) ./cordova/run --emulator does not start emulator image

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

ASF subversion and git services commented on CB-3627:
-----------------------------------------------------

Commit add107583f6cac15e226ed1612b761fadc2e5a46 in branch refs/heads/master from Fil Maj
[ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=add1075 ]

Proper modularization of bash scripts for [CB-3627], but not solved yet. wait_for_emulator does not work atm

                
> ./cordova/run --emulator does not start emulator image
> ------------------------------------------------------
>
>                 Key: CB-3627
>                 URL: https://issues.apache.org/jira/browse/CB-3627
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 2.8.0
>         Environment: Mac OSX 10.7.5
>            Reporter: Filip Maj
>            Assignee: Filip Maj
>             Fix For: 2.9.0
>
>
> Running
> {code}
> $ ./cordova/run --emulator
> {code}
> Successfully builds the project, but eventually stops with the following output:
> {code}
> No emulators found to deploy to. Please make sure your emulator is started
>  and you can view it using the 'cordova/lib/list-started-emulators' command.
> {code}
> Per the [Command Line Design document|http://wiki.apache.org/cordova/CommandLineToolingDesign] (see the section about multi-device flow near the top), when calling {{run}} with an emulator as a target, the {{run}} script should call {{start-emulator}} with the first available ID _if no emulator is currently running_.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira