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 086FA11E91 for ; Mon, 12 May 2014 18:29:13 +0000 (UTC) Received: (qmail 10898 invoked by uid 500); 12 May 2014 18:02:33 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 10860 invoked by uid 500); 12 May 2014 18:02:33 -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 10852 invoked by uid 500); 12 May 2014 18:02:33 -0000 Delivered-To: apmail-incubator-callback-dev@incubator.apache.org Received: (qmail 10849 invoked by uid 99); 12 May 2014 18:02:33 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 May 2014 18:02:33 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id EE0B016105; Mon, 12 May 2014 18:02:32 +0000 (UTC) From: martincgg To: callback-dev@incubator.apache.org Reply-To: callback-dev@incubator.apache.org References: In-Reply-To: Subject: [GitHub] cordova-mobile-spec pull request: CB-6669 Fix blackberry10 path Content-Type: text/plain Message-Id: <20140512180232.EE0B016105@tyr.zones.apache.org> Date: Mon, 12 May 2014 18:02:32 +0000 (UTC) Github user martincgg commented on the pull request: https://github.com/apache/cordova-mobile-spec/pull/63#issuecomment-42866117 Yes, that's right, Josh changes involved all platforms. The point is as I've explained at the previous comment, if you merge this: "blackberry10" : { "uri" : top_dir + "cordova-blackberry" + path.sep + "blackberry10" } it will brake for custom paths, I have tested that out a few weeks ago, and I've tested a few hours ago. Check the output at the previous comment or test it with createmobilespec, it will pass the req check, but not during addition of blackberry platform. --- 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. ---