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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.5.0
• Component/s: cordova-blackberry (DEPRECATED)
• Assignee: Josh Soref
• Reporter: Josh Soref
• Created: 03/Apr/14 21:45
• Updated: 09/Jun/14 19:36
• Resolved: 20/Apr/14 11:09

Description

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")