Return-Path: X-Original-To: apmail-cordova-issues-archive@minotaur.apache.org Delivered-To: apmail-cordova-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A077C10C6F for ; Wed, 12 Jun 2013 10:48:49 +0000 (UTC) Received: (qmail 78859 invoked by uid 500); 12 Jun 2013 10:48:49 -0000 Delivered-To: apmail-cordova-issues-archive@cordova.apache.org Received: (qmail 78840 invoked by uid 500); 12 Jun 2013 10:48:49 -0000 Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list issues@cordova.apache.org Received: (qmail 78831 invoked by uid 99); 12 Jun 2013 10:48:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jun 2013 10:48:49 +0000 Date: Wed, 12 Jun 2013 10:48:49 +0000 (UTC) From: "Shazron Abdullah (JIRA)" To: issues@cordova.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CB-2939) Add a ./cordova/run project-level script MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CB-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-2939: --------------------------------- Fix Version/s: (was: 2.8.0) 2.9.0 > Add a ./cordova/run project-level script > ---------------------------------------- > > Key: CB-2939 > URL: https://issues.apache.org/jira/browse/CB-2939 > Project: Apache Cordova > Issue Type: Improvement > Components: CLI > Reporter: Filip Maj > Assignee: Filip Maj > Fix For: 2.9.0 > > > {code} > run [--target=] > {code} > Deploys a build of the app to an available device or emulator. > Implicitly calls {{build}} first (see CB-2927). > If {{--target}} is specified, attempts to deploy the app to the device or emulator identified by . If the attempt fails, the script will error out with code 2 and an appropriate error message. If no {{--target}} is specified, follows this multi-device flow: > > # Are there any devices connected and available (should use the {{list-devices}} script TODO: [issue ref to come] to determine this)? If so, deploy to the first available one, if not continue. > # Are there any actual emulators available, i.e. started/running? (use {{list-started-emulators}} script TODO: [issue ref to come] to determine this). If so, target the first one. If no, continue. > # Are there any emulator images available to start? (use {{list-emulator-images}} script [CB-2947] to determine this). If so, call {{start-emulator }} TODO: [issue ref to come] of the first available image, wait for it to become ready, then deploy to it. > # If you get to this step, error out with a "no devices or emulators available" and exit with code 2. -- 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