Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of mmocny@google.com designates
 209.85.213.180 as permitted sender)
MIME-Version: 1.0
Sender: mmocny@google.com
In-Reply-To: 
 <CAE6O_-Y+au6tqxCPXm3ApomD=H8e8D9EL51mwqeN4F5=pio8Kg@mail.gmail.com>
References: <1405964044398.33111@adobe.com>
 <CAE6O_-Y+au6tqxCPXm3ApomD=H8e8D9EL51mwqeN4F5=pio8Kg@mail.gmail.com>
From: Michal Mocny <mmocny@chromium.org>
Date: Mon, 21 Jul 2014 14:42:38 -0400
Message-ID: 
 <CAEeF2Tc0OkAwGSw-1iahUcnH+UR=_jx+mxYpTOE9y8_X3rXHKQ@mail.gmail.com>
Subject: Re: When is .cordova created?
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=089e01183756d5501d04feb879b3

--089e01183756d5501d04feb879b3
Content-Type: text/plain; charset=UTF-8

That directory is optional.  It will only exist if you have non standard
config options.  When using --link-to and --copy-from, we set the config
option { "lib": { "www": { "uri": ..., link: true/false } } }.  We also set
config settings for e.g. Custom platform paths and plugin search paths.

Since Mark added the ability to specify search path from the command line,
and to add platforms by path directly, there are fewer and fewer reasons to
have a custom cordova config file.  (Also, do we really even needed the
lib.www.url setting saved in there when using --link-to/--copy-from?).
 Theres even an autoPersist setting which specifies if config file changes
should apply temporarily or be written out to disk.

There's also the question of how cordova config files *should* look like in
the future (see app config.xml vs platform config.xml vs
.cordova/config.json vs app manifest.json), or even what it means to be a
cordova workspace (see gulp/grunt workflow suggestions).

So, while I see the value of having one file that guarantees marking a
cordova project, I'm hesitant to mandate the existence of the .cordova
folder.  Up till now, we've been using
`cordovaLib.cordova.findProjectRoot()` to find the root of a cordova
project.  That helper should probably be improved a bit, but its worked
well enough in practice.  Its probably a good candidate for breaking out
into its own node package.

-Michal


On Mon, Jul 21, 2014 at 1:41 PM, Shazron <shazron@gmail.com> wrote:

> My guess is ever since hooks were moved out of .cordova to hooks/ the
> creation of .cordova by default wasn't removed also when using
> --copy-from.
>
> On Mon, Jul 21, 2014 at 10:34 AM, Ray Camden <raycamde@adobe.com> wrote:
> > (This question feels like it *should* be appropriate here, but if I
> should raise it on the PG Google group, I will.)
> >
> > I recently released a Brackets extension that wrapped calls to the
> Cordova CLI. I wrote some simple logic to handle checking if a folder is a
> Cordova project. I simply looked for a subdirectory called .cordova.
> >
> > But a user told me the extension wasn't correctly seeing a Cordova
> project and when I tested, it looks like the default cordova create command
> will not make the folder. It only exists (so far in my testing) if I create
> a new project and use --copy-from.
> >
> > Is there a reason why .cordova doesn't always exist?
> >
> > Worse comes to worse, I may just use some logic to see if platforms,
> plugins, and www exist as subdirectories.
>

--089e01183756d5501d04feb879b3--