You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Andrew Grieve (JIRA)" <ji...@apache.org> on 2013/12/11 16:53:07 UTC
[jira] [Reopened] (CB-4976) Don't use ~/.cordova/lib during
platform add when platform has been set to a local path via config.json
[ https://issues.apache.org/jira/browse/CB-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Grieve reopened CB-4976:
-------------------------------
Looks like this is still a problem when the user already has an existing dir in their ~/.cordova/libs, then even when it's overridden by a local path, it uses the ~/.cordova/libs version
> Don't use ~/.cordova/lib during platform add when platform has been set to a local path via config.json
> -------------------------------------------------------------------------------------------------------
>
> Key: CB-4976
> URL: https://issues.apache.org/jira/browse/CB-4976
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
> Reporter: Andrew Grieve
> Assignee: Braden Shepherdson
> Priority: Minor
>
> The caching of the platform within libs/ is a source of frustration to the continuous build, and to people constantly testing the tool locally against local platform checkouts. It causes you to sometimes not point to where you think it's pointing if the symlink already exists and it's different from what you specified in config.json.
> I think the best thing here would be to just not use the libs/ directory at all for the non-lazy-loaded case.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)