GitHub user shazron reopened a pull request:

    https://github.com/apache/cordova-ios/pull/305

    CB-8980 - Support <resource-file> tag in config.xml in iOS platform

    ### Platforms affected
    
    self
    
    ### What does this PR do?
    
    Support `<resource-file>` tag in config.xml  in iOS platform
    
    ### What testing has been done on this change?
    
    **NONE**. Work In Progress. Will update as I go along. 
    
    ### Checklist
    - [X] [Reported an issue](http://cordova.apache.org/contribute/issues.html) 
in the JIRA database
    - [X] Commit message follows the format: "CB-3232: (android) Fix bug with 
resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform 
affected.
    - [ ] Added automated test coverage as appropriate for this change.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shazron/cordova-ios CB-8980-b

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cordova-ios/pull/305.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 #305
    
----
commit 9a52b2fbede0f54c0e2209b2d2508108536a5f25
Author: Shazron Abdullah <[email protected]>
Date:   2017-04-14T00:31:02Z

    CB-8980 - Adding resource-file element to config.xml for iOS

commit 53f9ac809830296e9b98562900e404ca44096bd8
Author: Shazron Abdullah <[email protected]>
Date:   2017-04-17T18:51:32Z

    CB-8980 - Update bundled cordova-common to version 2.0.2

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to