[ 
https://issues.apache.org/jira/browse/CB-12861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Elliot Pryde updated CB-12861:
------------------------------
    Description: 
When invoking 'plugin add' on a plugin directory containing a plugin.xml, I 
would expect from 
https://cordova.apache.org/docs/en/latest/reference/cordova-cli/index.html#plugin-spec
 that 'cordova plugin add <relative path>' would work. This is the case on 
Windows, but on Linux I'm seeing that the call to 'plugin add' is resolving 
<relative path> as an npm plugin.

As a temporary working solution, you can move the plugin directory containing 
plugin.xml into the top level of the project directory before calling 'plugin 
add' (i.e. 'plugin add pluginXml-folder-name')


Error: Failed to fetch plugin ../cordova-map-launcher-plugin via registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Error: npm: Command failed with exit code 254 Error output:
npm ERR! addLocal Could not install 
/mnt/c/git/temp/project/cordova-map-launcher-plugin
npm ERR! Linux 3.4.0+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" 
"../cordova-map-launcher-plugin" "--save"
npm ERR! node v7.10.0
npm ERR! npm  v4.2.0
npm ERR! path /mnt/c/git/temp/project/cordova-map-launcher-plugin
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open

npm ERR! enoent ENOENT: no such file or directory, open 
'/mnt/c/git/temp/project/cordova-map-launcher-plugin'
npm ERR! enoent ENOENT: no such file or directory, open 
'/mnt/c/git/temp/project/cordova-map-launcher-plugin'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR!     /root/.npm/_logs/2017-05-26T14_25_53_966Z-debug.log

  was:
When invoking 'plugin add' on a plugin directory containing a plugin.xml, I 
would expect from 
https://cordova.apache.org/docs/en/latest/reference/cordova-cli/index.html#plugin-spec
 that 'cordova plugin add <relative path>' would work. This is the case on 
Windows, but on Linux I'm seeing that the call to 'plugin add' is resolving 
<relative path> as an npm plugin.


Error: Failed to fetch plugin ../cordova-map-launcher-plugin via registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Error: npm: Command failed with exit code 254 Error output:
npm ERR! addLocal Could not install 
/mnt/c/git/temp/project/cordova-map-launcher-plugin
npm ERR! Linux 3.4.0+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" 
"../cordova-map-launcher-plugin" "--save"
npm ERR! node v7.10.0
npm ERR! npm  v4.2.0
npm ERR! path /mnt/c/git/temp/project/cordova-map-launcher-plugin
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open

npm ERR! enoent ENOENT: no such file or directory, open 
'/mnt/c/git/temp/project/cordova-map-launcher-plugin'
npm ERR! enoent ENOENT: no such file or directory, open 
'/mnt/c/git/temp/project/cordova-map-launcher-plugin'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR!     /root/.npm/_logs/2017-05-26T14_25_53_966Z-debug.log


As a temporary working solution, you can move the plugin directory containing 
plugin.xml into the top level of the project directory before calling 'plugin 
add' (i.e. 'plugin add pluginXml-folder-name')


> Linux add plugin to project from file system outside of project directory
> -------------------------------------------------------------------------
>
>                 Key: CB-12861
>                 URL: https://issues.apache.org/jira/browse/CB-12861
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-cli, cordova-plugins
>    Affects Versions: [email protected]
>         Environment: Linux
>            Reporter: Elliot Pryde
>
> When invoking 'plugin add' on a plugin directory containing a plugin.xml, I 
> would expect from 
> https://cordova.apache.org/docs/en/latest/reference/cordova-cli/index.html#plugin-spec
>  that 'cordova plugin add <relative path>' would work. This is the case on 
> Windows, but on Linux I'm seeing that the call to 'plugin add' is resolving 
> <relative path> as an npm plugin.
> As a temporary working solution, you can move the plugin directory containing 
> plugin.xml into the top level of the project directory before calling 'plugin 
> add' (i.e. 'plugin add pluginXml-folder-name')
> Error: Failed to fetch plugin ../cordova-map-launcher-plugin via registry.
> Probably this is either a connection problem, or plugin spec is incorrect.
> Check your connection and plugin name/version/URL.
> Error: npm: Command failed with exit code 254 Error output:
> npm ERR! addLocal Could not install 
> /mnt/c/git/temp/project/cordova-map-launcher-plugin
> npm ERR! Linux 3.4.0+
> npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" 
> "../cordova-map-launcher-plugin" "--save"
> npm ERR! node v7.10.0
> npm ERR! npm  v4.2.0
> npm ERR! path /mnt/c/git/temp/project/cordova-map-launcher-plugin
> npm ERR! code ENOENT
> npm ERR! errno -2
> npm ERR! syscall open
> npm ERR! enoent ENOENT: no such file or directory, open 
> '/mnt/c/git/temp/project/cordova-map-launcher-plugin'
> npm ERR! enoent ENOENT: no such file or directory, open 
> '/mnt/c/git/temp/project/cordova-map-launcher-plugin'
> npm ERR! enoent This is most likely not a problem with npm itself
> npm ERR! enoent and is related to npm not being able to find a file.
> npm ERR! enoent
> npm ERR! Please include the following file with any support request:
> npm ERR!     /root/.npm/_logs/2017-05-26T14_25_53_966Z-debug.log



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to