Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Date: Sun, 20 Apr 2014 11:10:16 +0000 (UTC)
From: "Bryan Higgins (JIRA)" <jira@apache.org>
To: issues@cordova.apache.org
Message-ID: <JIRA.12706513.1396561558201.144817.1397992216799@arcas>
In-Reply-To: <JIRA.12706513.1396561558201@arcas>
References: <JIRA.12706513.1396561558201@arcas>
Subject: [jira] [Closed] (CB-6398) Support command arguments for
 blackberry-nativepackager, blackberry-debugtokenrequest and
 blackberry-deploy in blackberry10.json
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CB-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Higgins closed CB-6398.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 3.5.0

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