[ 
https://issues.apache.org/jira/browse/CB-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995233#comment-13995233
 ] 

ASF GitHub Bot commented on CB-6669:
------------------------------------

Github user martincgg commented on the pull request:

    https://github.com/apache/cordova-mobile-spec/pull/63#issuecomment-42857438
  
    @shazron it's the same problem.
    I've contributed with createmobilespec.js and I've faced this problem with 
blackberry10.
    This is what happens when this path (this fix):
    "blackberry10" : { "uri" : top_dir + "cordova-blackberry" + path.sep + 
"blackberry10" }
    it's set in config.json.
    
    Output:
    Adding Platform: blackberry10
    Checking if platform "blackberry10" passes minimum requirements...
    Creating blackberry10 project...
    Running command: cmd /s /c 
C:\Users\Administrator\testMB\cordova-blackberry\blackberry10\blackberry10\bin\create
 C:\Users\Administrator\testMB\mobilespec\platforms\blackberry10 
org.apache.mobilespec mobilespec
    The system cannot find the path specified.
    Command finished with error code 1: cmd 
/s,/c,C:\Users\Administrator\testMB\cordova-blackberry\blackberry10\blackberry10\bin\create,C:\Users\Administrator\testMB\mobilespec\platforms\blackberry10,org.apache.mobilespec,mobilespec
    Error: cmd: Command failed with exit code 1
        at ChildProcess.whenDone 
(C:\Users\Administrator\testMB\cordova-cli\src\supe
    rspawn.js:126:23)
        at ChildProcess.EventEmitter.emit (events.js:98:17)
        at maybeClose (child_process.js:753:16)
        at Process.ChildProcess._handle.onexit (child_process.js:820:5)
    
    The problem is that the blackberry10_parser.js it doesn't look for the 
subdirectory 'blackberry10' under cordova-blackberry.
    Then later when it tries to create the project it's not gonna pass through 
here:
    
https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/lazy_load.js#L63
    Because lazy_loads.js it looks for the subdirectory under cordova-blackberry
    
    Result if you set this path: "blackberry10" : { "uri" : top_dir + 
"cordova-blackberry" + path.sep + "blackberry10" }
    At project creation lazy_loads.js it will try to set the custom library as: 
cordova-blackberry\blackberry10\blackberry10\
    
    The blackberry10_parser.js it makes fail the requirements check because it 
doesn't look for 'blackberry10' folder under cordova-blackberry.


> createmobilespec.js doesn't work with the blackberry10 option
> -------------------------------------------------------------
>
>                 Key: CB-6669
>                 URL: https://issues.apache.org/jira/browse/CB-6669
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: mobile-spec
>            Reporter: Shazron Abdullah
>            Assignee: Bas Bosman
>
> In the root folder of all my repos:
> {code}
> ./cordova-mobile-spec/createmobilespec/createmobilespec.js --blackberry10
> {code}
> I get this error:
> {code}
> 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 
> "/Users/shaz/Documents/Git/Apache/mobilespec"
> Using custom www assets from 
> /Users/shaz/Documents/Git/Apache/cordova-mobile-spec
> /Users/shaz/Documents/Git/Apache/mobilespec /Users/shaz/Documents/Git/Apache
> Adding platforms...
> Adding Platform: blackberry10
> Checking if platform "blackberry10" passes minimum requirements...
> Requirements check failed: /bin/sh: 
> /Users/shaz/Documents/Git/Apache/cordova-blackberry/bin/check_reqs: No such 
> file or directory
> {code}
> Note here that check_reqs should be in 
> `Users/shaz/Documents/Git/Apache/cordova-blackberry/*blackberry10*/bin/check_reqs`



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to