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

Support multiple level dependance #16

Open
Chren opened this issue Dec 14, 2019 · 1 comment
Open

Support multiple level dependance #16

Chren opened this issue Dec 14, 2019 · 1 comment

Comments

@Chren
Copy link

Chren commented Dec 14, 2019

Hi, we have pod structure as below:

ModuleA.podspec
s.dependency 'AFNetworking'

MergeFile:

group 'Networking' has_dependencies! pod 'AFNetworking' pod 'CustomNetwork', :path => "../../../path" end

Podfile

target 'target' do
pod 'Networking', :path => 'MergedPods/Networking'
pod 'ModuleA'
end

After run 'bundle exec pod install'
I got two AFNetworking in pod project.
One is under Development Pods, another is under Pods, how to solve it?

@Chren Chren changed the title Support mult Support multiple level dependance Dec 14, 2019
@biocross
Copy link

Hello,

Thanks for reporting this. Unfortunately this is something the plugin cannot handle, since it'll not modify dependencies outside of the MergeFile.

One way to fix this in your case is to also try merging ModuleA into the Networking group:

group 'Networking' 
    has_dependencies! 
    pod 'AFNetworking' 
    pod 'CustomNetwork', :path => "../../../path"
    pod 'ModuleA' 
end

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

2 participants