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

Update plugin guide to mention plural path keys.

Browse source
This commit is contained in:
Phil Hagelberg 2012-02-22 16:56:11 -08:00
parent ae37356845
commit c34c912c09
1 changed files with 22 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
doc/PLUGINS.md
View file

@ -170,6 +170,9 @@ version of Clojure from within a Leiningen plugin, you can use
'(println "hello from" *clojure-version*)) '(println "hello from" *clojure-version*))
``` ```
In Leiningen 1.x, plugins had access to monolithic Clojure Contrib.
This is no longer true in 2.x.
## Upgrading Existing Plugins ## Upgrading Existing Plugins
Earlier versions of Leiningen had a few differences in the way plugins Earlier versions of Leiningen had a few differences in the way plugins
@ -219,20 +222,31 @@ plugin provides an example of a compatibility shim:
```clj ```clj
(defn eval-in-project (defn eval-in-project
"Support eval-in-project in both Leiningen 1.x and 2.x." "Support eval-in-project in both Leiningen 1.x and 2.x."
[& args] [project form init]
(let [eip (or (try (require 'leiningen.core.eval) (let [[eip two?] (or (try (require 'leiningen.core.eval)
(resolve 'leiningen.core.eval/eval-in-project) [(resolve 'leiningen.core.eval/eval-in-project)
(catch java.io.FileNotFoundException _)) true]
(try (require 'leiningen.compile) (catch java.io.FileNotFoundException _))
(resolve 'leiningen.compile/eval-in-project) (try (require 'leiningen.compile)
(catch java.io.FileNotFoundException _)))] [(resolve 'leiningen.compile/eval-in-project)]
(apply eip args))) (catch java.io.FileNotFoundException _)))]
(if two?
(eip project form init)
(eip project form nil nil init))))
``` ```
Of course if the function has changed arities or has disappeared Of course if the function has changed arities or has disappeared
entirely this may not be feasible, but it should suffice in most entirely this may not be feasible, but it should suffice in most
cases. cases.
Another key change is that `:source-path`, `:resources-path`,
`:java-source-path`, and `:test-path` have changed to
`:sources-paths`, `:resource-paths`, `:java-source-paths`, and
`:test-paths`, and they should be vectors now instead of single
strings. The old `:dev-resources` key is now just another entry to the
`:resource-paths` vector that's only present when the `:dev` profile
is active.
Allowing the task to run outside a project directory is tricky to do Allowing the task to run outside a project directory is tricky to do
in a backwards-compatible way since 1.x is overly-clever and actually in a backwards-compatible way since 1.x is overly-clever and actually
inspects your argument list to figure out if it should pass in a inspects your argument list to figure out if it should pass in a