Copyright (c) 2015 Jonathan Dixon.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
That was the intended purpose of
platform-merges
. This directory should follow the same structure asplatforms
, but only contains customizations that need to be version controlled. The contents of theplatform-merges
directory will be copied toplatforms
, replacing any Cordova generated content. For example to customize theplist
file for iOS, make the changes in xcode (or in any editor) and copy the file toplatform-merges/ios/App/App-Info.plist
.Be aware that any file in
platform-merges
will clobber its counterpart inplatforms
when any grunt command that callscopy:platform-merges
is run. There is still plenty of room for improvement in this process, but IMO it is still better than adding the entireplatforms
directory to version control.