@@ -318,19 +318,18 @@ contains among other things a full stacktrace.
318
318
319
319
First make sure you have Leiningen 2.9 .1 or later, `lein upgrade` if necessary.
320
320
321
- ` lein version`
321
+ lein version
322
322
323
323
To work with `mranderson` the first thing to do is:
324
324
325
- ` lein do clean, inline-deps`
325
+ lein do clean, inline-deps
326
326
327
327
this creates the munged local dependencies in target/srcdeps directory
328
328
329
329
after that you can run your tests or your repl with:
330
330
331
- `lein with-profile +plugin.mranderson/config repl`
332
-
333
- `lein with-profile +plugin.mranderson/config test`
331
+ lein with-profile +plugin.mranderson/config repl
332
+ lein with-profile +plugin.mranderson/config test
334
333
335
334
note the plus sign before the leiningen profile.
336
335
@@ -339,21 +338,18 @@ If you want to use `mranderson` while developing locally with the repl the sourc
339
338
When you want to release
340
339
locally:
341
340
342
- ` lein with-profile plugin.mranderson/config install`
341
+ lein with-profile plugin.mranderson/config install
343
342
344
343
to clojars:
345
344
346
- `lein with-profile plugin.mranderson/config deploy clojars`
347
-
348
- Or alternatively run
349
-
350
- `make install`
345
+ lein with-profile plugin.mranderson/config deploy clojars
351
346
352
- `make deploy`
347
+ Alternatively you can leverage the bundled `Makefile`:
353
348
354
- build.sh cleans, runs source-deps with the right parameters, runs the tests and then runs the provided lein target.
349
+ make install
350
+ make deploy
355
351
356
- You can also use a Makefile now: `make clean && make test` for example .
352
+ You might also want to do a `make test` prior to deploying anything to Clojars .
357
353
358
354
## Changelog
359
355
0 commit comments