[ https://issues.apache.org/jira/browse/CB-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025623#comment-14025623 ]
ASF GitHub Bot commented on CB-6398: ------------------------------------ Github user jsoref closed the pull request at: https://github.com/apache/cordova-blackberry/pull/153 > 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 > Fix For: 3.5.0 > > > 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)