Open dirtyvagabond opened 9 years ago
Potential fix courtesy @stfactual :
On project.clj line 32, [com.cemerick/pomegranate "0.2.0" :exclusions [org.apache.httpcomponents/httpcore]] works for me. It failed when excluding the one from the S3 library.
I can't explain your original bug as stated, but I can explain something similar. clj-s3 and pomegranate each bring in a different version of httpcore (4.2 for s3, 4.1.x for pomegranate). Drake failed for any plugins.edn when I excluded 4.2, so I instead excluded 4.1.x. That made it work both for the existing library and for nonexisting.
If you have a library in your local Maven repository, it's possible it wouldn't make an HTTP request. That might be the reason things worked when your library existed. I used [funnyplaces "1.2.3"], which wasn't in my local repo but does exist on clojars, and it failed.
This error message looks more like a version mismatch. Are you sure it comes from non-existent artifacts? On Jun 24, 2015 10:39 AM, "Aaron Crow" notifications@github.com wrote:
Potential fix courtesy @stfactual https://github.com/stfactual :
On project.clj line 32, [com.cemerick/pomegranate "0.2.0" :exclusions [org.apache.httpcomponents/httpcore]] works for me. It failed when excluding the one from the S3 library.
I can't explain your original bug as stated, but I can explain something similar. clj-s3 and pomegranate each bring in a different version of httpcore (4.2 for s3, 4.1.x for pomegranate). Drake failed for any plugins.edn when I excluded 4.2, so I instead excluded 4.1.x. That made it work both for the existing library and for nonexisting.
If you have a library in your local Maven repository, it's possible it wouldn't make an HTTP request. That might be the reason things worked when your library existed. I used [funnyplaces "1.2.3"], which wasn't in my local repo but does exist on clojars, and it failed.
— Reply to this email directly or view it on GitHub https://github.com/Factual/drake/issues/178#issuecomment-114950844.
No, not sure at all. In Spencer's quote, he's suggesting it can happen when Pomegranate triggers a dep request over the wire
If a non-existent artifact is specific in the plugins file, Drake explodes with an incredibly arcane and unhelpful stack trace.
Example
plugins.edn
:Yields: