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

Resolve custom repositories #4

Open
julienfantin opened this issue Feb 28, 2017 · 1 comment
Open

Resolve custom repositories #4

julienfantin opened this issue Feb 28, 2017 · 1 comment

Comments

@julienfantin
Copy link

One of our transitive dependencies pulls from a custom repository [1] which seems to confuse vizdeps, erroring with:

clojure.lang.ExceptionInfo: Exception processing dependencies of [cc.qbits/alia-all "3.3.0" :exclusions [[org.clojure/tools.reader]]]: Exception processing dependencies of [cc.qbits/alia-eaio-uuid "3.1.3"]: Exception processing dependencies of [cc.qbits/tardis "1.0.0"]: Exception processing dependenci
es of [com.eaio.uuid/uuid "3.3"]: Exception resolving dependencies of [com.eaio.uuid/uuid "3.3"]: Could not resolve dependencies
...
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact com.eaio.uuid:uuid:jar:3.3 in central (https://repo1.maven.org/maven2/)

The command runs once we had the repository to our own project however.

[1] https://github.com/mpenet/tardis/blob/master/project.clj

@hlship
Copy link
Member

hlship commented Mar 8, 2017

There's a hack in there to resolve artifacts that may have an issue. I think I've seen this in some of our internal code, we're generally good about identifying external repos in each project.clj, but something dragged in some JBoss stuff only visible to in the JBoss repos and I had to explicit add that to :repositories in some roll-up projects.

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

No branches or pull requests

2 participants