Leiningen用于自动化Clojure项目，而不会让你无法忍受。(Leiningen is for automating Clojure projects without setting your hair on fire.)
Leiningen（发音：LINE-ing-en. ['laɪnɪŋən]）是使用Clojure的最简单的方法。 专注于项目自动化和声明性配置，它脱颖而出，让您专注于您的代码。
\r\n
(defproject leiningen.org "1.0.0"\r\n :description "Generate static HTML for https://leiningen.org"\r\n :dependencies [[enlive "1.0.1"]\r\n [cheshire "4.0.0"]\r\n [org.markdownj/markdownj "0.3.0-1.0.2b4"]]\r\n :main leiningen.web)\r\n
| Name With Owner | technomancy/leiningen |
|---|---|
| Primary Language | Clojure |
| Program language | Shell (Language Count: 9) |
| Platform | |
| License: | Other |
| Created At | 2009-11-01 05:50:07 |
|---|---|
| Pushed At | 2025-04-16 18:59:45 |
| Last Commit At | 2022-06-15 21:03:55 |
| Release Count | 82 |
| Last Release Name | 2.11.2 (Posted on 2024-02-13 16:41:31) |
| First Release Name | 0.5.0 (Posted on ) |
| Stargazers Count | 7.3k |
|---|---|
| Watchers Count | 220 |
| Fork Count | 1.6k |
| Commits Count | 5k |
| Has Issues Enabled | |
| Issues Count | 1919 |
| Issue Open Count | 95 |
| Pull Requests Count | 746 |
| Pull Requests Open Count | 7 |
| Pull Requests Close Count | 151 |
| Has Wiki Enabled | |
|---|---|
| Is Archived | |
| Is Fork | |
| Is Locked | |
| Is Mirror | |
| Is Private |
"Leiningen!" he shouted. "You're insane! They're not creatures you can
fight—they're an elemental—an 'act of God!' Ten miles long, two
miles wide—ants, nothing but ants! And every single one of them a
fiend from hell..."
- from Leiningen Versus the Ants by Carl Stephenson
Leiningen is for automating Clojure projects without setting your hair on fire.
If your preferred
package manager
offers a recent version of Leiningen, try that first as long as it has version 2.x.
Leiningen installs itself on the first run of the lein shell script; there is no
separate install script. Follow these instructions to install Leiningen manually:
lein script from the stable branch$PATH. (~/bin is a good choice if it is on your path.)chmod +x ~/bin/lein)Windows users can use the above script in the Linux subsystem or try
the batch file or
Powershell version
instead.
The
tutorial
has a detailed walk-through of the steps involved in creating a new
project, but here are the commonly-used tasks:
$ lein new [TEMPLATE] NAME # generate a new project skeleton
$ lein test [TESTS] # run the tests in the TESTS namespaces, or all tests
$ lein repl # launch an interactive REPL session
$ lein run -m my.namespace # run the -main function of a namespace
$ lein uberjar # package the project and dependencies as standalone jar
$ lein deploy clojars # publish the project to Clojars as a library
Use lein help to see a complete list. lein help $TASK shows the
usage for a specific task.
You can also chain tasks together in a single command by using the
do task with comma-separated tasks:
$ lein do clean, test foo.test-core, jar
Most tasks need to be run from somewhere inside a project directory to
work, but some (new, help, search, version, and repl) may
run from anywhere.
The project.clj file in the project root should look like this:
(defproject myproject "0.5.0-SNAPSHOT"
:description "A project for doing things."
:license "Eclipse Public License 1.0"
:url "http://github.com/technomancy/myproject"
:dependencies
:plugins )
The lein new task generates a project skeleton with an appropriate
starting point from which you can work. See the
sample.project.clj
file (also available via lein help sample) for a detailed listing of
configuration options.
The project.clj file can be customized further with the use of
profiles.
Leiningen documentation is organized as a number of guides:
Leiningen supports plugins which may introduce new tasks. See
the plugins wiki page
for a full list. If a plugin is needed for successful test or build
runs, (such as lein-tar) then it should be added to :plugins in
project.clj, but if it's for your own convenience (such as
lein-pprint) then it should be added to the :plugins list in the
:user profile in ~/.lein/profiles.clj. See the
profiles guide
for details on how to add to your :user profile. The
plugin guide
explains how to write plugins.
Source Copyright © 2009-2018 Phil Hagelberg, Alex Osborne, Dan Larkin, and
contributors.
Distributed under the Eclipse Public License, the same as Clojure
uses. See the file COPYING.
Thanks to Stuart Halloway for Lancet and Tim Dysinger for convincing
me that good builds are important.
Images Copyright © 2010 Phil Hagelberg. Distributed under the Creative
Commons Attribution + ShareAlike
License. Full-size version
available.
