[
https://issues.apache.org/jira/browse/CB-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819466#comment-13819466
]
Braden Shepherdson commented on CB-5347:
----------------------------------------
We recently modified the lazy loading code to not symlink into ~/.cordova/lib
when you point it at a local path; instead it just copies directly from the
local path. This is in the newest release of CLI, which is not tagged as
"latest" on npm yet. You could install it with "npm install -g
[email protected]".
If you're putting symlinks into lib/ for other reasons, could you explain what
those reasons are?
Also Josh, that logic in the PR looks backwards. If it can successfully read
the link, we throw an error? Shouldn't it be retrieving the link's path, then
checking whether it exists?
> Cordova returns unknown errors messages when symlinks are pointing to bad
> locations
> -----------------------------------------------------------------------------------
>
> Key: CB-5347
> URL: https://issues.apache.org/jira/browse/CB-5347
> Project: Apache Cordova
> Issue Type: Bug
> Reporter: JennyGee
> Priority: Minor
>
> Steps to reproduce:
> 1. npm install cordova
> 2. cordova create project
> 3. cd project
> 4. cordova platform add firefoxos
> 5. cordova platform remove firefoxos
> 6. mv ~/.cordova/lib/firefoxos/cordova/3.1.0
> ~/.cordova/lib/firefoxos/cordova/3.1.0-orig
> 7. ln -s /no/such/firefoxos ~/.cordova/lib/firefoxos/cordova/3.1.0
> 8. cordova platform add firefoxos
> Actual result:
> Error that comes back that doesn't really say what is wrong:
> shell.js: internal error
> Error: EEXIST, file already exists '~/.cordova/lib/firefoxos/cordova/3.1.0'
> Expected result:
> Some sort of error that says something like this:
> [Error: Unable to fetch platform blackberry10:
> ~/.cordova/lib/firefoxos/cordova/3.1.0 points to non-existent or unreadable
> location: /no/such/firefoxos]
--
This message was sent by Atlassian JIRA
(v6.1#6144)
