Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 71BC011712 for ; Thu, 24 Jul 2014 15:43:54 +0000 (UTC) Received: (qmail 50254 invoked by uid 500); 24 Jul 2014 15:43:54 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 50213 invoked by uid 500); 24 Jul 2014 15:43:54 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 50202 invoked by uid 99); 24 Jul 2014 15:43:53 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jul 2014 15:43:53 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id 9DF569B2E84; Thu, 24 Jul 2014 15:43:53 +0000 (UTC) From: dylin To: dev@cordova.apache.org Reply-To: dev@cordova.apache.org References: In-Reply-To: Subject: [GitHub] cordova-blackberry pull request: CB-7186 --no-signing will be igno... Content-Type: text/plain Message-Id: <20140724154353.9DF569B2E84@tyr.zones.apache.org> Date: Thu, 24 Jul 2014 15:43:53 +0000 (UTC) Github user dylin commented on the pull request: https://github.com/apache/cordova-blackberry/pull/169#issuecomment-50036071 we transform ww 2.0 style arguments to ww 1.0 style and pass them to packager, there are no a corresponding things for --no-singing in packager side. the cli front end decide signing or not by --no-signing flag, however the back end (package_validator) check it by -g && -buildId, that's why it will omit --no-signing when --buildId was specified. cmdline.js parses the transformed args, and signing flag here will be used in package-validator.js, and won't be passed to packager (because packager doesn't has `signing` option). --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---