[
https://issues.apache.org/jira/browse/CB-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492556#comment-13492556
]
Kevin Hawkins commented on CB-1822:
-----------------------------------
What are the details around removing/moving VERSION? With our current
framework, which consumes Cordova and presents our own "version" of a hybrid
app framework, it's helpful that the version is parseable, as we do not make
use of the Cordova app creation template/code, so we have to recreate this
process to a degree.
Can we keep the version information as something that's somewhat externally
parseable, as opposed to, say, tightly coupling it with the creation script?
> Move cordova.ios.js to CordovaLib directory
> -------------------------------------------
>
> Key: CB-1822
> URL: https://issues.apache.org/jira/browse/CB-1822
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Reporter: Andrew Grieve
> Assignee: Andrew Grieve
> Priority: Minor
> Fix For: 2.3.0
>
>
> Relevant ML thread: http://callback.markmail.org/thread/5m5qiv3vokwyuxyo
> This change involves:
> 1. Move from bin/templates/project/www/{cordova-VERSION.js to
> CordovaLib/cordova.ios.js
> 2. Remove VERSION from bin/templates/project/www/index.html
> 3. Move VERSION-adding logic from Makefile into the create script, and have
> it also copy the .js from the new location
> 4. Delete CordovaLibTests/CordovaLibApp/www/cordova.ios.js
> 5. Add a build phase to CordovaLibApp to copy the .js file into it's www
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
