-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Feature request - Support for CocoaPods registries #9690
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
Comments
what is an example of "breakage"? We tend to ensure we follow semver guidelines and not ship breaking changes. |
@dnkoutso, |
The current title of this issue is a bit misleading, because we're actually not proposing to support Artifactory specifically. We think it makes more sense for CocoaPods to support any CocoaPods registry vendor. This would allow others to build their own CocoaPods proxies, and would greatly benefit the CocoaPods community. I'm therefore changing the title of this issue to "Feature request - Support for CocoaPods registries". We've started looking into implementing this and hope we can get your feedback for a pull request we'll submit. We'd really appreciate any feedback, questions or requests you may already have for this initiative, |
While in general this is definitely a good Idea to better support tools like Artifactory for proxying available libraries and making local builds faster and also reliable (in case of unavailable master repo, unpublished libraries) I think it doesn't really make sense to do that for the old style repository anymore. This is slow, takes a lot of space locally and in the end the CDN is/will be the preferred way (as far as I understood). Therefor it should rather be possible to enable this for CocoaPods CDN which is as well not supported by Artifactory as of now: https://www.jfrog.com/jira/browse/RTFACT-20455 |
Thanks for you comment and suggestion @pschneider! |
hey @eyalbe4 and others! Apologies for the long delay here. Past month I wasnt able to spend time on CocoaPods... I think a proposal would make sense here in either direction and I would be glad to review PRs and the proposal itself to support it first-class within CocoaPods. |
Hi @dnkoutso - thanks for your feedback! |
sounds good! |
@eyalbe4 Is there a specification of the expected behavior for these registries? - I'd be a bit worried about merging in support for this without the expectations being documented |
Sure, I completely agree. @yahavi added the usage details for the new functionality in the description of #9959 but please let us know where you would like us to document the specification. Also, if there's a preferred format or convention for the documenting the specification, please let us know and we'll make sure to follow it. Thanks |
Any updates here? Would love this for 1.11.0 release. |
@dnkoutso, |
@endocrimes @dnkoutso |
Going to close this in favor of #9994! I do not think a separate issue adds anything more than the RFC. |
JFrog Artifactory supports managing CocoaPods packages, through its CocoaPods Repositories. Since CocoaPods does not support Artifactory natively, the cocoapods-art gem is currently used for this integration. Since this is an external plugin, it can break, following changes implemented in Cocoapods.
We suggest adding native Artifactory support to CocoaPods, so that it can seamlessly work with Artifactory CocoaPods Repositories, like any other repository.
We are willing to contribute this functionality through a pull request.
The text was updated successfully, but these errors were encountered: