@@ -12,18 +12,18 @@ be configurable enough that such things can be done through modifications in the
12
12
13
13
## Installation
14
14
15
- Put ` [lein-shell "0.4.0 "] ` into the ` :plugins ` vector of your ` :user ` profile
15
+ Put ` [lein-shell "0.4.1 "] ` into the ` :plugins ` vector of your ` :user ` profile
16
16
inside ` ~/.lein/profiles.clj ` if you want to use lein shell on a per user basis
17
17
(this doesn't * really* make much sense, but you're allowed to if you want to!).
18
18
19
19
To explicitly say that this project needs lein-shell to be built, putt
20
- ` [lein-shell "0.4.0 "] ` into the ` :plugins ` vector of your ` project.clj ` . If you
20
+ ` [lein-shell "0.4.1 "] ` into the ` :plugins ` vector of your ` project.clj ` . If you
21
21
have no ` :plugins ` vector in your ` project.clj ` , it should look like this:
22
22
23
23
``` clj
24
24
(defproject your-project-here " version"
25
25
...
26
- :plugins [[lein-shell " 0.4.0 " ]]
26
+ :plugins [[lein-shell " 0.4.1 " ]]
27
27
... )
28
28
```
29
29
@@ -68,7 +68,7 @@ uberjaring, testing and repl'ing, I can do this:
68
68
:prep-tasks [[" shell" " generator" " --in" " build/in.grammar"
69
69
" --out" " src/out.clj" ]
70
70
" javac" " compile" ]
71
- :plugins [[lein-shell " 0.4.0 " ]])
71
+ :plugins [[lein-shell " 0.4.1 " ]])
72
72
```
73
73
74
74
Now, the command ` generator --in build/in.grammar --out src/out.clj ` will always
@@ -102,7 +102,7 @@ that:
102
102
``` clj
103
103
(defproject package.name /project " 0.1.0-SNAPSHOT"
104
104
...
105
- :plugins [[lein-shell " 0.4.0 " ]]
105
+ :plugins [[lein-shell " 0.4.1 " ]]
106
106
:aliases {" javadoc" [" shell" " javadoc" " -d" " javadoc"
107
107
" -sourcepath" " src/" " package.name" ]
108
108
" jar" [" do" " javadoc," " jar" ]}}})
0 commit comments