Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Date: Tue, 31 Jan 2012 05:01:11 +0000 (UTC)
From: "Gary Bentley (Created) (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: 
 <1309609109.10515.1327986071138.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (CB-209) Improve ios upgrade procedure to take
 burden off of end developer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Improve ios upgrade procedure to take burden off of end developer
-----------------------------------------------------------------

                 Key: CB-209
                 URL: https://issues.apache.org/jira/browse/CB-209
             Project: Apache Callback
          Issue Type: Improvement
          Components: iOS
    Affects Versions: 1.3.0
         Environment: IOS
            Reporter: Gary Bentley
            Assignee: Shazron Abdullah
            Priority: Critical


Currently to upgrade phone gap to a new version it is recommended that you create a completely new phone gap project and then migrate your settings across to the new project.

This is problematic for a number of reasons:

1. There are many settings that have to be transfered, including splash images and icons, external hosts, code signing setup, orientations and more.  It is onerous to have to manually set these up every time you want to use a new version of phone gap.

2. It breaks your source control since the new project is not under source control, it also breaks your archives within XCode.

Compare this with upgrading to a new phone gap version for Android where all you need to do is change the .jar and .js file.

Having to manually re-create your project for a new version in ios is a significant barrier and can be a huge time sync.

What is needed is an upgrade mechanism that is similar to Android, the end developer should not be re-creating a project for new versions.

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