Return-Path: 
 <issues-return-2558-apmail-cordova-issues-archive=cordova.apache.org@cordova.apache.org>
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 8534FF9E7
	for <apmail-cordova-issues-archive@minotaur.apache.org>;
 Mon,  8 Apr 2013 04:47:17 +0000 (UTC)
Received: (qmail 42868 invoked by uid 500); 8 Apr 2013 04:47:16 -0000
Delivered-To: apmail-cordova-issues-archive@cordova.apache.org
Received: (qmail 42793 invoked by uid 500); 8 Apr 2013 04:47:16 -0000
Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cordova.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cordova.apache.org>
List-Post: <mailto:issues@cordova.apache.org>
List-Id: <issues.cordova.apache.org>
Reply-To: dev@cordova.apache.org
Delivered-To: mailing list issues@cordova.apache.org
Received: (qmail 42765 invoked by uid 99); 8 Apr 2013 04:47:16 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Apr 2013 04:47:16 +0000
Date: Mon, 8 Apr 2013 04:47:16 +0000 (UTC)
From: "Filip Maj (JIRA)" <jira@apache.org>
To: issues@cordova.apache.org
Message-ID: <JIRA.12641304.1365396382361.125864.1365396436336@arcas>
In-Reply-To: <JIRA.12641304.1365396382361@arcas>
References: <JIRA.12641304.1365396382361@arcas>
Subject: [jira] [Created] (CB-2946) Add a ./cordova/run project-level script
 for OSX
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

Filip Maj created CB-2946:
-----------------------------

             Summary: Add a ./cordova/run project-level script for OSX
                 Key: CB-2946
                 URL: https://issues.apache.org/jira/browse/CB-2946
             Project: Apache Cordova
          Issue Type: Sub-task
          Components: OSX
            Reporter: Filip Maj
            Assignee: Shazron Abdullah
             Fix For: 2.7.0


{code}
run [--target=<id>]
{code}

Deploys a build of the app to an available device or emulator.

Implicitly calls {{build}} first (see CB-2934).

If {{--target}} is specified, attempts to deploy the app to the device or emulator identified by <id>. 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 TODO: [issue ref to come] to determine this). If so, call {{start-emulator <id>}} 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