Geek asks and answers

How do you customize your own dependencies for Leiningen?

We are working on a project with several Clojure -Java interop. At the moment, we have one class that has many dependencies that we put in the user library in Eclipse for development, but, of course, this does not help when using Leiningen (2.x). Most of our dependencies are property, so they are not located somewhere in the repository.

What is the easiest / right way to do this?

I saw leiningen - how to add dependencies for local cans? but it looks like it's out of date?

Update: So, I created a local maven repository for my jar, after these instructions and documents for deploying lein to github, and edited the project.clj file as follows:

:dependencies [[...]
               [usc "0.1.0"]]
:repositories {"usc" "file://maven_repository"}

Where maven_repository is in the project directory (hence not used file:///). When I launched "lein deps" - I received this message:

Retrieving usc/usc/0.1.0/usc-0.1.0.pom from usc
Could not transfer artifact usc:usc:pom:0.1.0 from/to usc (file://maven_repository): no supported algorithms found
This could be due to a typo in :dependencies or network issues.
Could not resolve dependencies

What is meant by “lack of supported algorithms” and how to fix it?

Update2: Found last bit of response here .

+5
source share
3 answers

leiningen. . , , , , , , .

+1

@ , , , , .

  • Repeatability. , , , , .

  • - , , . -, , , lein , clojure S3 , . Maven Ant Maven S3. technomancy s3 wagon private, clojars , .

  • , @Arthur , lein install. , , .m2, . maven .m2 ( , ?), , , , . , localRepository node $M2_HOME/conf/settings.xml , . . .

+1

YMMV, Maven, Leiningen, Polyglot Clojure/Java.

This is mainly because Java tools (Eclipse, etc.) understand Maven projects, but they don’t really understand Leiningen projects. It is getting better with the excellent Clojure counterclockwise plugin, but the integration is still not good enough for an efficient IDE-based workflow.

On the repository side, I propose creating a private shared Maven repository. You will need this sooner or later if you plan to manage a complex set of dependencies within your team: you can also bite a bullet and do it now.

0
source

More articles:


All Articles