-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cocoapods support improvement #108
Conversation
0fef465
to
9a96445
Compare
Any info about the new method? |
Thanks @jcesarmobile . This proposal introduces new tag (I don't plan to introduce In order to develop this feature, I will improve For example, I plan to introduce new methods
I will improve |
9a96445
to
8ad9cf4
Compare
Hi! Not sure if this is related, but is there a way to add a Cocoapods My use case is: we use Artifactory CocoaPods proxy to resolve dependencies behind a corporate firewall. The Artifactory documentation specifies to make this work, you have to add this to the
Is this achievable with your changes @knight9999 ? |
@mattdsteele If you want to get the Podfile:
Your plugin.xml should have
i.e. To specify |
Merged as the support improvements were already integrated and released. |
The purpose of this ticket is to improve Cocoapod support by:
type="podspec"
The current
framework
tagtype="podspec"
provided basic CocoaPods support in the beginning. Continuing to support this method but expand on the tag to support more features will become messy. Additionally, some configurations are not at an individual pod level.In this case, the best option is to deprecate this method and implement a new method for handling CocoaPods.
The new method/structure in
plugin.xml
will improve the readability.The new method/structure in
plugin.xml
will also provide the ability to give users flexibility with global pod configuration and down to the individual pods.Goals