Add Settings.bundle containing acknowledgements if CocoaPods is enabled

[bitcrumb]

Add Settings.bundle which contains CocoaPods 'Acknowledgements' section (updated on every pod install) as well as an entry containing the version & build number (updated on each build).

[bitcrumb]

Afterthought: I should still add an option to the cli to allow anyone to enable/disable this feature.

[bitcrumb]

Did quite a refactor to be able to put everything behind the enable_settings option. Downside is that you lose the flexibility of specifying where the Settings.bundle should go in your project structure (but that's not that big of a tradeoff I guess, except that it assumes a 'Resources' group).

Also note that the CFBundleVersionand the CFBundleShortVersionStringare updated in the Info.plist of the generated build & not in the Info.plist of the project itself, since that would require the ability to insert a shell script build phase before the 'Copy Bundle Resources'. Something which isn't possible at the moment out-of-the-box (so I didn't bother at the moment).

Any feedback & assistance is appreciated @gfontenot, since I am pretty new to Ruby & this project. Keep up the good work, this is an awesome tool and I'd love to contribute even more.

[gfontenot]

Slick. Thanks for this. I'm wondering if we shouldn't make the acknowledgement bit conditional to CocoaPods being enabled. That would give users a bit more control over the setup of their project. They could (for example) keep the settings bundle enabled, but disable CocoaPods and end up with an empty settings bundle, or they could disable the settings bundle and keep CocoaPods enabled and end up with no attribution.

[bitcrumb]

Good point, you're correct that users will now end up with an empty Acknowledgements sections if they decide to disable CocoaPods support. I'll have to look into how I can dynamically include/exclude this from the Root.plist. Or maybe I could supply two different Setting.bundle files in the templates folder (one with and one without the Acknowledgments section) & move one or the other depending on what the user chose. I'll have a look at this later today. Note that the Settings.bundle will never be empty, there's always going to be a Version entry. Should this be optional as well?

[gfontenot]

You can use ERB for this fairly easy. A conditional block in ERB would look like this:

<% if use_cocoapods %>
# stuff
<% end %>

Note the lack of = in the ERB tag. This would make ERB execute the code, but not print the result.

Regarding the version entry: I feel like I'd prefer to not include that by default. It's something that can easily be overridden in a custom plist locally if needed.

[bitcrumb]

Thanks, I'll update this pull request with your feedback as soon as I find the time.

[bitcrumb]

I removed the automatic addition of version info & updated the file manager so that files inside directories get parsed as well (needed to use ERB inside Root.plist of the Settings.bundle).

[gfontenot]

Don't need the . here.

[bitcrumb]

Will fix.

[bitcrumb]

Code changes after your feedback have been pushed. Only thing remaining is the code duplication remark. Any suggestions?

[gfontenot]

None that would be within the scope of this PR. I think a larger refactor of the xcodeproj_helper and project classes is probably needed.

If you can rebase this down into a single commit, I'll get it into master.

[bitcrumb]

Done.

[gfontenot]

Awesome, thanks. Tweaked the commit message a little and merged in a2d9d90