Return-Path: 
 <dev-return-24976-apmail-cordova-dev-archive=cordova.apache.org@cordova.apache.org>
X-Original-To: apmail-cordova-dev-archive@www.apache.org
Delivered-To: apmail-cordova-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3F4CD1056F
	for <apmail-cordova-dev-archive@www.apache.org>;
 Wed, 24 Jul 2013 14:06:21 +0000 (UTC)
Received: (qmail 97283 invoked by uid 500); 24 Jul 2013 14:06:21 -0000
Delivered-To: apmail-cordova-dev-archive@cordova.apache.org
Received: (qmail 97258 invoked by uid 500); 24 Jul 2013 14:06:20 -0000
Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cordova.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cordova.apache.org>
List-Post: <mailto:dev@cordova.apache.org>
List-Id: <dev.cordova.apache.org>
Reply-To: dev@cordova.apache.org
Delivered-To: mailing list dev@cordova.apache.org
Received: (qmail 97249 invoked by uid 99); 24 Jul 2013 14:06:20 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jul 2013 14:06:20 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of tommy@devgeeks.org designates
 209.85.212.181 as permitted sender)
Received: from [209.85.212.181] (HELO mail-wi0-f181.google.com)
 (209.85.212.181)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jul 2013 14:06:14 +0000
Received: by mail-wi0-f181.google.com with SMTP id hq4so489135wib.14
        for <dev@cordova.apache.org>; Wed, 24 Jul 2013 07:05:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:x-originating-ip:in-reply-to:references:date
         :message-id:subject:from:to:content-type:x-gm-message-state;
        bh=F+tbMduIJCx4slJfVl3LCrz2TfYw37HjQhcKlYjIlIU=;
        b=RncKYVzkukcsLHNH6rzEb3HmWh5yAcXU4hdOUuvk38pXcQPgTusU1e+JvnLQgDdiBC
         CXitS4ArJ0K0Blg/CHGK2+hcXxyTYOpy4XuQXt4Ayx+1FFy0kEGazisRY8SzZt1cwPuI
         aPMSdiNS8Hm1hVD58/VHPZzUkv4N8m12hQHlbkS9aZo27ndFv5BuC0EQ0kB1+oFAYO/p
         o92cyfcjRaAU4Y1sysnQVw8V+xbl2mkrStc06FwJmpcUrdXdD44TPQUq4+cuO7wr6xME
         BCOF2JC/uTo0yFZ0jCYbpDxd3CWWep+na6Esijv4BIQa1fOWdPnFgcmw8AKx/5lr8cpP
         oYFQ==
MIME-Version: 1.0
X-Received: by 10.180.72.134 with SMTP id d6mr2836011wiv.8.1374674753986; Wed,
 24 Jul 2013 07:05:53 -0700 (PDT)
Received: by 10.180.7.201 with HTTP; Wed, 24 Jul 2013 07:05:53 -0700 (PDT)
X-Originating-IP: [208.54.5.253]
Received: by 10.180.7.201 with HTTP; Wed, 24 Jul 2013 07:05:53 -0700 (PDT)
In-Reply-To: 
 <CAK_TSXJSj+K=PKrRw0Y_PerpsfEGjuEqoKFJ80jfU8FmNvX2Yg@mail.gmail.com>
References: 
 <CAMTxO42Hjt+iVZNeecWNPzg0uGuwwV0C99c8jox6Tyeod8dfVw@mail.gmail.com>
	<CAK_TSXJSj+K=PKrRw0Y_PerpsfEGjuEqoKFJ80jfU8FmNvX2Yg@mail.gmail.com>
Date: Wed, 24 Jul 2013 07:05:53 -0700
Message-ID: 
 <CAPTyS6Bwbh=q+DneRyar45W4WcUMvaJae+LQTAJ0RWAw9Ytn-w@mail.gmail.com>
Subject: Re: cordova-cli - run command
From: Tommy Williams <tommy@devgeeks.org>
To: dev@cordova.apache.org
Content-Type: multipart/alternative; boundary=f46d0434390864b83b04e242680a
X-Gm-Message-State: 
 ALoCoQmec55ox1NRHRub6M9h/Y16HaA081JnW7+r9JfX81imGccQLyrO7HkB83F3sXKM4zqu7DN8
X-Virus-Checked: Checked by ClamAV on apache.org

--f46d0434390864b83b04e242680a
Content-Type: text/plain; charset=ISO-8859-1

Yeah, seems odd that prepare,compile is nearly impossible to avoid.
On 24 Jul 2013 07:03, "Ian Clelland" <iclelland@chromium.org> wrote:

> I think what I'd like to see is this:
>
> cordova run <platform>: prepare, compile, deploy
> cordova deploy <platform>: deploy only (existing compiled app)
>
> Then we can make the published preferred workflow just "edit your code in
> www; cordova run <platform> to test", while still exposing the low-level
> interface for developers who know what they're doing, and want control over
> the prepare/compile/deploy cycle.
>
> Ian
>
>
> On Wed, Jul 24, 2013 at 9:02 AM, David Kemp <drkemp@google.com> wrote:
>
> > The run command in cli is documented (in help) as 'deploys an app'.
> > The code in fact does a prepare, then deploy.
> >
> > This seems a little odd, since the normal cycle would be
> > prepare,compile,deploy.
> > Is this behavior intentional, or was this changed in error in CB-3460?
> >
>

--f46d0434390864b83b04e242680a--