Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Date: Fri, 29 Jun 2012 17:02:44 +0000 (UTC)
From: "Shazron Abdullah (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: <2048155396.72225.1340989364210.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <2132185938.9583.1334091920892.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CB-479) iOS Upgrade Guide: Add upgrade path for
 existing project(s) on how to replace "cordova.framework" by "cordova
 subproject"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Shazron Abdullah updated CB-479:
--------------------------------

      Component/s: Docs
    Fix Version/s:     (was: 1.9.0)
                   2.0.0
          Summary: iOS Upgrade Guide: Add upgrade path for existing project(s) on how to replace "cordova.framework" by "cordova subproject"  (was: Create a manual for existing project(s) on how to replace "cordova.framework" by "cordova subproject")
    
> iOS Upgrade Guide: Add upgrade path for existing project(s) on how to replace "cordova.framework" by "cordova subproject"
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CB-479
>                 URL: https://issues.apache.org/jira/browse/CB-479
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Docs, iOS
>    Affects Versions: 1.6.0
>         Environment: IOS XCODE MAC
>            Reporter: Emile khattar
>            Assignee: Shazron Abdullah
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> If you already created a cordova .framework project using the cordova template in xcode and you would like to move into a subproject based solution a manual is needed to make it faster.
> Tips from a personal experience:
> - Unlink the cordova framework
> - Un-install cordova framework to make sure the migration went well (then re-install)
> - unset this variable "CORDOVA_FRAMEWORK=YES" from the build settings
> - grep for "#ifdef CORDOVA_FRAMEWORK" in the plugins code to make sure that you are importing the files correctly.
> - Empty the value of "framework search paths" in the build settings 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira