How to manage conflicts with duplicate dependencies (the same module gets defined twice)

[Bartosz Kalinowski]

I've started a question on SO about my problem so I won't go into much details here. In general I have trouble with the same module getting defined twice in dependent projects. 

Please check it out:

http://stackoverflow.com/questions/38213089/duplicate-protocol-implementations-in-dependent-projects

For me it seems like a bigger issue with dependencies. Is there some way I could solve this from my code side (like not modifying dependencies)?

Also I am able to modify one of them (not Ecto obviously) but what would be the best practice here? To avoid having the same module defined twice

Regards

[Bartosz Kalinowski]

Hey guys, I've started bounty on this question as I think it really should get more love and deserves some ideas how to solve the problem with implementing Protocols for the same other types in different projects. Please give it some thoughts! :)