You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Josh Soref (JIRA)" <ji...@apache.org> on 2014/04/03 23:47:18 UTC

[jira] [Created] (CB-6398) Support command arguments for blackberry-nativepackager, blackberry-debugtokenrequest and blackberry-deploy in blackberry10.json

Josh Soref created CB-6398:
------------------------------

             Summary: Support command arguments for blackberry-nativepackager, blackberry-debugtokenrequest and blackberry-deploy in blackberry10.json
                 Key: CB-6398
                 URL: https://issues.apache.org/jira/browse/CB-6398
             Project: Apache Cordova
          Issue Type: Bug
          Components: BlackBerry
    Affects Versions: 3.4.0
            Reporter: Josh Soref
            Assignee: Josh Soref


blackberry-signer and blackberry-debugtokenrequest support configuring a proxy, however 3.4.0 doesn't expose this.

With this change, this file:

cat ~/.cordova/blackberry10.json 
{
    "blackberry-signer": {
        "-proxyhost": "localhost",
        "-proxyport": "8100"
    },
    "blackberry-debugtokenrequest": {
        "-proxyhost": "localhost",
        "-proxyport": "8100"
    },
    "blackberry-nativepackager": {
    },
    "blackberry-deploy": {
    },
    "this-field-is-ignored": true
}

Will result in proxy connections by blackberry-signer and blackberry-debugtokenrequest to a proxy running on localhost:8100 -- if it's answering.

With these changes, you could in theory include "-debugNative": "" as a param for blackberry-deploy [I'm not sure why you would].

With these changes, you could in theory include "-buildId": "42" as a param for blackberry-nativepackager (or use the less well documented "-buildIdFile": "/absolute/path/to/buildIdFile")



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