What steps will reproduce the problem?
1. Add a :repositories option to your project.clj.
2. Add a ^:replace keyword to it
https://github.com/technomancy/leiningen/blob/master/sample.project.clj#L76
3. Update dependencies.
What is the expected output? What do you see instead?
Expected is that it will NOT try to contact Maven Central. I see it does try to
contact Maven Central. This may be a problem if central.maven.org isn't
reachable (corporate intranet) or if your own repo has a jar with the same name
as Maven Central but different content that is supposed to override Maven's
version (I do that.)
What version of the product are you using? On what operating system?
0.31.1
Please provide any additional information below.
This was a bug in Leiningen 2.4.0 - 2.5.0 and has been fixed in 2.5.1.
https://github.com/technomancy/leiningen/issues/1695 Which Leiningen jar is in
CCW 0.31.1? Such information should be published somewhere so that Leiningen
bugs can be correlated with CCW bugs. Anyways I tried forcing Leiningen 2.5.1
by specifying a custom leiningen.jar in Preferences but strangely strangely
this didn't change anything.
Original issue reported on code.google.com by e...@mailup.net on 13 Feb 2015 at 1:02
Original issue reported on code.google.com by
e...@mailup.neton 13 Feb 2015 at 1:02