yogsototh/leiningen
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #2196 from technomancy/cprice404-managed-deps-docs-re-exclusions

Browse source 
Add clarification re: `:exclusions` in managed dependencies docs
This commit is contained in:
Jean Niklas L'orange 2016-09-01 22:19:24 +02:00 committed by GitHub
commit c1991be03c
1 changed files with 14 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
doc/MANAGED_DEPS.md
View file

@ -53,6 +53,20 @@ directly in the `:dependencies` section. The feature becomes more powerful
when your build workflow includes some other way of sharing the `:managed-dependencies` when your build workflow includes some other way of sharing the `:managed-dependencies`
section across multiple projects. section across multiple projects.
## A note on modifiers (`:exclusions`, `:classifier`, etc.)
The managed dependencies support in leiningen *does* work with modifiers such as `:exclusions` and `:classifier`. However, at present, because of the way that lein and pomegranate process the args in the dependencies vector, you will need to explicitly specify `nil` as the value for the version arg in order to achieve this:
```clj
(defproject superfun/happyslide "1.0.0-SNAPSHOT"
:description "A Clojure project with managed dependencies"
:min-lein-version "2.7.0"
:managed-dependencies [[clj-time "0.12.0"]]
:dependencies [[clj-time nil :exclusions [foo]]])
```
Issue #2195 covers the possibility of doing some future work to allow omission of the `nil` in the example above.
## Lein "parent" projects ## Lein "parent" projects
One way of leveraging `:managed-dependencies` across multiple projects is to use One way of leveraging `:managed-dependencies` across multiple projects is to use