Strange Dependency Resolution Principle

[GoogleCodeExporter]

Counterclockwise 0.29.0

1. Assume for some reason the dependencies cannot be fetched from repositories, 
e.g. issue #653.
2. The following workaround should be possible: Fetch dependencies via "lein 
deps" on console. Then a refresh of the project or "Update Dependencies" should 
grab these deps from local ".m2".

But this does not work for the project dependencies. I suggest that even in 
error scenarios CCW finally looks up all referenced (project.clj) libraries in 
the local ".m2" folder and adds them to the "Leiningen Dependencies" properly. 
Each library that is missing in ".m2" should be displayed as an "Error". The 
failure of a remote lookup for a library that is present locally in ".m2" in 
the specified version can be displayed as a "Warning".

This would enable the "leiningen on console" fallback for all potential future 
problems.

The repl launched via leiningen still works as expected since it does not care 
about what is listed in "Leiningen Dependencies".

Original issue reported on code.google.com by Gunnar.V...@googlemail.com on 4 Nov 2014 at 12:38

[GoogleCodeExporter]

Indeed. In fact, i intend at some point to totally ditch the embedded 
leiningen, and only communicate with leiningen launched as an external process.
This should then solve the last pieces not behaving the same.

We may lost some feature during the move (e.g. there are some tricks done for 
downloading source / jar files, hmmm).

Not sure about your suggestion. There are still open questions. Leaving it new 
since it's interesting food for thoughts, thanks !

Original comment by laurent....@gmail.com on 6 Nov 2014 at 3:16

[GoogleCodeExporter]

Original comment by laurent....@gmail.com on 6 Nov 2014 at 3:16

• Added labels: lein