Skip to content
This repository has been archived by the owner on Apr 25, 2024. It is now read-only.

conflicts with same artifact name in different group #149

Open
dehubbed opened this issue Jun 12, 2016 · 4 comments
Open

conflicts with same artifact name in different group #149

dehubbed opened this issue Jun 12, 2016 · 4 comments
Labels

Comments

@dehubbed
Copy link

I'm trying to build an app that contains spongycastle and zxing. I have spongycastle in my dependencies first, and then as soon as I add zxing classes from spongycastle are not found anymore. They both have a maven artifact with the artifactId "core", but different groupIds of course, hence think there is a conflict.

I changed the artifactId of zxing from "core" to "zxcore" and now it works. So it is definitely the artifactId that's the problem.

@bendlas
Copy link

bendlas commented Jun 13, 2016

I spent some 3 hours, blaming everything from clojure to leiningen, until I independently arrived at this ticket. Here is a clear demonstration of the issue: https://github.com/bendlas/lein-resolution-failure

thanks to @noisesmith for helping to narrow this down

@bendlas
Copy link

bendlas commented Jun 13, 2016

Here

grouped (group-by :name tagged)
we need a more intelligent grouping function. Just consdering artefacts with the same name to be equal is clearly insufficient. Maybe there should be a user-configurable replacement map that defines groups whose artefacts are "interchangeable".

@alexander-yakushev
Copy link
Contributor

This was done this way so that one can easily replace some Android-incompatible dependency with a customly built one.

I'll have to think about it. Perhaps additional parameter is necessary to state which dependencies should override others.

@bendlas
Copy link

bendlas commented Jun 14, 2016

Maybe a simple additional artefact paramter would do the trick. Something like [custom/clojure "1.8.0" :supersedes org.clojure/clojure]

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

No branches or pull requests

3 participants