[
https://issues.apache.org/jira/browse/CB-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880318#comment-13880318
]
ASF subversion and git services commented on CB-5782:
-----------------------------------------------------
Commit 2676ff88a8b547d9542bc51e9e0b18bd6966ef4d in branch refs/heads/master
from [~kamrik]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=2676ff8 ]
CB-5782 Use CordovaError wherever relevant.
Other than the trivial changes that look like
new Error(...) -> new CordovaError(...)
there is also a change in util.js to throw the error instead of returning it
and associated changes in specs.
> Catch exceptions and print nice error when cordova-cli run from a non cordova
> project.
> --------------------------------------------------------------------------------------
>
> Key: CB-5782
> URL: https://issues.apache.org/jira/browse/CB-5782
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
> Reporter: Michal Mocny
> Assignee: Mark Koudritsky
> Priority: Minor
>
> cordova prepare prints scary stack trace when run from the wrong directory.
> This is likely a common error and we should make it clear what is happening.
> Seems we are already catching the case, just failing to report it gracefully:
> throw new Error('Current working directory is not a Cordova-based
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
