Josh Soref created CB-6339:
------------------------------
Summary: platform Dependencies should be fetched eagerly or
searchpath should be stored or ...
Key: CB-6339
URL: https://issues.apache.org/jira/browse/CB-6339
Project: Apache Cordova
Issue Type: Bug
Components: Plugman
Reporter: Josh Soref
{quote}
$ cordova plugin add com.blackberry.sensors --searchpath
../cordova-blackberry-plugins/plugin/
$ cordova plugin
[ 'com.blackberry.sensors' ]
$ cordova platform add blackberry10
Creating blackberry10 project...
npm WARN package.json jWorkflow@0.8.0 No repository field.
npm WARN package.json localize@0.4.2 No repository field.
Installing "com.blackberry.sensors" for blackberry10
Fetching plugin "com.blackberry.utils" via plugin registry
Installing "com.blackberry.utils" for blackberry10
{quote}
The intention here is clearly to have the plugin and its dependencies installed
from {{--searchpath}}.
Having to add platforms before adding plugins or having to remember that
{{--searchpath}} doesn't work for platforms that aren't yet present is pretty
painful.
If you don't want to implement any persistence for the {{--searchpath}}, then,
at least trawl through the platform dependencies and warn when they won't do
the right thing.
As in:
{quote}
*WARNING*: {{com.blackberry.utils}} will not be installed from
{{../cordova-blackberry-plugins/plugin/com.blackberry.utils}} when you run
{{cordova platform add blackberry10}}
{quote}
For reference, the sensors plugin.xml file has:
{quote}
<platform name="blackberry10">
<dependency id="com.blackberry.utils" />
...
</platform>
{quote}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
