GitHub user BBosman opened a pull request:
https://github.com/apache/cordova-mobile-spec/pull/63
CB-6669 Fix blackberry10 path
The blackberry10 code doesn't reside in the root of the blackberry
respository, as is the case with the other platform repositories.
This commit adds the required blackberry10 subdirectory to the config.json
written by createmobilespec.js
Output after calling
```
cordova-mobile-spec\createmobilespec\createmobilespec.js --blackberry10
```
```
Creating project. If you have any errors, it may be from missing
repositories.
To clone needed repositories (android as an example):
./cordova-coho/coho repo-clone -r plugins -r mobile-spec -r android -r cli
To update all repositories:
./cordova-coho/coho repo-update
Creating project mobilespec...
Creating a new cordova project with name "MobileSpec_Tests" and id
"org.apache.cordova.mobilespec" at location "C:\GitHub\mobilespec"
Using custom www assets from C:\GitHub\cordova-mobile-spec
C:\GitHub\mobilespec C:\GitHub
Adding platforms...
Adding Platform: blackberry10
Checking if platform "blackberry10" passes minimum requirements...
Requirements check failed: blackberry-nativepackager cannot be found on the
path. Aborting.```
```
I don't have the blackberry10 toolset installed, so check_req fails, but
check_req is now at least invoked. :)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BBosman/cordova-mobile-spec CB-6669
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-mobile-spec/pull/63.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #63
----
commit 12c29a5e4f6af1a5703f511aea159620603d0ad1
Author: Bas Bosman <git...@nazgul.nu>
Date: 2014-05-10T11:59:41Z
Fix path
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
