Return-Path: X-Original-To: apmail-cordova-issues-archive@minotaur.apache.org Delivered-To: apmail-cordova-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4A26C11646 for ; Thu, 10 Apr 2014 17:34:18 +0000 (UTC) Received: (qmail 66816 invoked by uid 500); 10 Apr 2014 17:34:18 -0000 Delivered-To: apmail-cordova-issues-archive@cordova.apache.org Received: (qmail 66794 invoked by uid 500); 10 Apr 2014 17:34:17 -0000 Mailing-List: contact issues-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 issues@cordova.apache.org Received: (qmail 66737 invoked by uid 99); 10 Apr 2014 17:34:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Apr 2014 17:34:15 +0000 Date: Thu, 10 Apr 2014 17:34:15 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@cordova.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CB-6415) Make project/.cordova/config.json integrate with platforms.js MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CB-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965575#comment-13965575 ] ASF GitHub Bot commented on CB-6415: ------------------------------------ GitHub user jsoref opened a pull request: https://github.com/apache/cordova-cli/pull/162 CB-6415 Make project/.cordova/config.json integrate with platforms.js You can merge this pull request into a Git repository by running: $ git pull https://github.com/blackberry/cordova-cli cb_6415 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-cli/pull/162.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #162 ---- commit 171b6afaf986e9fdc5048c354e4ed5edccc6eae9 Author: Josh Soref Date: 2014-04-09T16:59:50Z CB-6415 Make project/.cordova/config.json integrate with platforms.js ---- > Make project/.cordova/config.json integrate with platforms.js > ------------------------------------------------------------- > > Key: CB-6415 > URL: https://issues.apache.org/jira/browse/CB-6415 > Project: Apache Cordova > Issue Type: Bug > Components: CLI > Affects Versions: 3.4.0 > Environment: Windows 7, Native development environment for blackberry10 properly configured. > Reporter: Martin Gonzalez > Assignee: Martin Gonzalez > Labels: blackberry10, cli > Fix For: 3.5.0 > > > Working on some tests, for a new node module for cordova, I've found a problem when I try to work with custom libraries, this problem only applies to Blackberry, it doesn't resolve correctly a uri path in a config.json file, > My configuration in the project: > .cordova/config.json ----> > { > "id": "org.apache.cordova", > "name": "mobilespec", > "lib": { > "blackberry10": { > "uri": "C:\\Users\\Administrator\\cordova-blackberry" > }, > "wp8": { > "uri": "C:\\Users\\Administrator\\cordova-coho\\cordova-wp8" > }, > "windows8": { > "uri": "C:\\Users\\Administrator\\cordova-coho\\cordova-windows" > } > } > } > The problem is that it never resolves the path, with the folder that contains blackberry10 library, which is inside of cordova-blackberry. > When I try to add the full path to the project: > "blackberry10":{"uri":"C:\\Users\\Administrator\\cordova-coho\\cordova-blackberry\\blackberry10"} > It pass the requirements check, but when it produce an error at running the command to add the project at superspawn.js. > What's happening here is, that it pass the requirements check, but when it try to use the library use is trying to use this path: C:\\Users\\Administrator\\cord > ova-blackberry\\blackberry10\\blackberry10\\bin\\create > So the usage path is obtained trying to look for 'blackberry10', under 'cordova-blackberry', and the requirements check requires the whole path: "blackberry10":{"uri":"C:\\Users\\Administrator\\cordova-coho\\cordova-blackberry\\blackberry10"} > According to my trace, the requirements check it should resolve the path correctly, looking under 'cordova-blackberry'. > I'll assign this to me, I have a simple solution for it when custom paths are used. -- This message was sent by Atlassian JIRA (v6.2#6252)