[
https://issues.apache.org/jira/browse/CB-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759147#comment-13759147
]
Braden Shepherdson commented on CB-4748:
----------------------------------------
I've marked CB-4578 as a duplicate of this. That bug is mostly the same, though
not quite.
I think the correct behavior between both of them is:
- Fail fast and with a clear error message if the target directory already
exists.
- Kill the behavior where it uses the current directory if the directory is
unspecified. I'm not even sure if that's documented, and it's confusing.
- A bare "cordova create" should show at least an error explaining the correct
syntax.
> `cordova create` should fail fast when directory already exists
> ---------------------------------------------------------------
>
> Key: CB-4748
> URL: https://issues.apache.org/jira/browse/CB-4748
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0
> Reporter: Andrew Grieve
> Assignee: Mark Koudritsky
> Priority: Minor
>
> Running "cordova create" twice with the same args results in:
> {code}
> $ cordova create CordovaAppHarness org.apache.appharness CordovaAppHarness
> $ cordova create CordovaAppHarness org.apache.appharness
> {code}
> {code}
> mkdir: path already exists:
> /Users/agrieve/git/cordova/cordova-app-harness/CordovaAppHarness/.cordova/hooks/after_build
> mkdir: path already exists:
> /Users/agrieve/git/cordova/cordova-app-harness/CordovaAppHarness/.cordova/hooks/after_compile
> mkdir: path already exists:
> /Users/agrieve/git/cordova/cordova-app-harness/CordovaAppHarness/.cordova/hooks/after_docs
> mkdir: path already exists:
> /Users/agrieve/git/cordova/cordova-app-harness/CordovaAppHarness/.cordova/hooks/after_emulate
> mkdir: path already exists:
> /Users/agrieve/git/cordova/cordova-app-harness/CordovaAppHarness/.cordova/hooks/after_platform_add
> mkdir: path already exists:
> /Users/agrieve/git/cordova/cordova-app-harness/CordovaAppHarness/.cordova/hooks/after_platform_rm
> ...
> {code}
> The second run should just fail with an error message.
--
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