Skip to content
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

Push to cocoapods #15

Closed
erkie opened this issue Mar 9, 2015 · 21 comments
Closed

Push to cocoapods #15

erkie opened this issue Mar 9, 2015 · 21 comments

Comments

@erkie
Copy link

erkie commented Mar 9, 2015

I see there is a podspec file but Alamofire-SwiftyJSON is not a available on cocoapods.org. It seems to be possible to have swift dependencies on cocoapods using cocoapods 0.36.0.

Could you push it?

@cellularmitosis
Copy link

+1

3 similar comments
@marcus30
Copy link

marcus30 commented Apr 3, 2015

+1

@alec-c4
Copy link

alec-c4 commented Apr 13, 2015

+1

@ippy04
Copy link

ippy04 commented Apr 17, 2015

+1

@nickkjordan
Copy link

until then:
pod 'Alamofire-SwiftyJSON', :git => "https://github.com/SwiftyJSON/Alamofire-SwiftyJSON.git"

@minhoryang
Copy link

+1

2 similar comments
@cheebow
Copy link

cheebow commented May 12, 2015

+1

@sambecker
Copy link

+1

@sambecker
Copy link

@nickkjordan I tried that solution and running pod install did successfully add Alamofire-SwiftyJSON to my Xcode project, however, I cannot import the class or use the .responseSwiftyJSON method/extension. Have you had any similar issues?

@nickkjordan
Copy link

@sambecker I was able to import using import Alamofire_SwiftyJSON

@josafafilho
Copy link

+1

@hemincong
Copy link

@jk
Copy link

jk commented Aug 5, 2015

+1

@tangplin Can we help you to push your work to CocoaPods? I would like to help.

@matt-lebl
Copy link

+1

@kostiakoval
Copy link

pod 'Alamofire-SwiftyJSON' doesn't contains Alamofire and SwiftyJSON as dependencies :(

s.dependency 'Alamofire'
s.dependency 'SwiftyJSON'

@gabovanlugo
Copy link

+1

1 similar comment
@pcoulter
Copy link

+1

@erkie
Copy link
Author

erkie commented Sep 18, 2015

Was this fixed with #28?

@nickkjordan
Copy link

@erkie No

@jettandres
Copy link

+1

@wongzigii
Copy link
Member

Closing for inactive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests