cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Soref (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CB-6124) cordova plugin remove x fails if there's a plugin whose directory was deleted
Date Thu, 27 Feb 2014 19:05:20 GMT
Josh Soref created CB-6124:
------------------------------

             Summary: cordova plugin remove x fails if there's a plugin whose directory was
deleted
                 Key: CB-6124
                 URL: https://issues.apache.org/jira/browse/CB-6124
             Project: Apache Cordova
          Issue Type: Bug
          Components: Plugman
    Affects Versions: 3.4.0
            Reporter: Josh Soref


$ cordova plugin remove org.apache.cordova.battery-status
Uninstalling org.apache.cordova.battery-status from android
Error: ENOENT, no such file or directory 'mobilespec/plugins/com.blackberry.pim.lib/plugin.xml'
    at Object.fs.openSync (fs.js:427:18)
    at Object.fs.readFileSync (fs.js:284:15)
    at Object.module.exports.parseElementtreeSync (cordova-plugman/src/util/xml-helpers.js:119:27)
    at cordova-plugman/src/util/dependencies.js:22:35
    at Array.forEach (native)
    at Object.module.exports.generate_dependency_info (cordova-plugman/src/util/dependencies.js:21:45)
    at Object.module.exports.dependents (cordova-plugman/src/util/dependencies.js:38:46)
    at runUninstall (cordova-plugman/src/uninstall.js:105:35)
    at Function.module.exports.uninstallPlatform (cordova-plugman/src/uninstall.js:39:12)
    at cordova-cli/src/plugin.js:164:58
mobilespec $ ls plugins/com.blackberry.pim.lib
ls: plugins/com.blackberry.pim.lib: No such file or directory

Expected results: Just because a plugin doesn't exist doesn't mean you can't build a graph.
Especially if the goal is to delete stuff.

Note: I'm only using cordova plugin remove to delete things (and cordova plugin add to add),
so whomever either added it incompletely or failed to properly remove it is partially to blame,
but my goal right now is safe handling of bad states, not investigating how I got to the bad
state.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message