[
https://issues.apache.org/jira/browse/CB-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868418#comment-13868418
]
Jared Flatow commented on CB-5347:
----------------------------------
This is still an issue for me. I need to use relative symlinks for icons in an
app in a git repository, in order to avoid maintaining two copies of icons.
Shouldn't cordova follow symlinks when you are building and not copy links that
might get broken? Wouldn't it be nice to guarantee that the build directory is
self-contained?
> 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
> Assignee: Josh Soref
> 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.5#6160)
