Browse files

Update paths of documentation files.

  • Loading branch information...
1 parent 7988e56 commit 2cb7ec9af48b1a094848a5e9963ea201015a5645 @technomancy committed Jul 6, 2011
Showing with 8 additions and 8 deletions.
  1. +4 −4
  2. +1 −1 doc/
  3. +1 −1 doc/
  4. +2 −2 doc/
@@ -41,7 +41,7 @@ and use self-install.
## Usage
has a detailed walk-through of the steps involved in creating a new
project, but here are the commonly-used tasks:
@@ -131,7 +131,7 @@ See the plugin task's help for more information.
**Q:** What's a group ID? How do snapshots work?
**A:** See the
- [tutorial](
+ [tutorial](
for background.
**Q:** How should I pick my version numbers?
@@ -143,14 +143,14 @@ See the plugin task's help for more information.
is a typo in your :dependency declaration in project.clj.
**Q:** What if my project depends on jars that aren't in any repository?
-**A:** The [deploy guide](
+**A:** The [deploy guide](
explains how to set up a private repository. If you are not sharing
them with a team you could also just [install locally.](
**Q:** How do I write my own tasks?
**A:** If it's a task that may be useful to more than just your
project, you should make it into a
- [plugin](
+ [plugin](
You can also include one-off tasks in your src/leiningen/ directory
if they're not worth spinning off; the plugin guide shows how.
@@ -2,7 +2,7 @@
Getting your library into [Clojars]( is fairly
straightforward as is documented near the end of
-[the Leiningen tutorial](
+[the Leiningen tutorial](
However, deploying is not always as straightforward as the process
described there.
@@ -21,7 +21,7 @@ TODO: what goes where? a tour through the launching of a task
Leiningen is extensible; you can define new tasks in plugins. Add your
plugin as a dev-dependency of your project, and you'll be able to call
-<tt>lein $YOUR_COMMAND</tt>. See the [plugins guide]( for details.
+<tt>lein $YOUR_COMMAND</tt>. See the [plugins guide]( for details.
The [mailing list]( and the
leiningen or clojure channels on Freenode are the best places to
@@ -416,7 +416,7 @@ on your production servers.
If your project is a library and you would like others to be able to
use it as a dependency in their projects, you will need to get it into
a public repository. While it's possible to
-[maintain your own private repository](
+[maintain your own private repository](
or get it into Maven central, the easiest way is to publish it at
[Clojars]( Once you have created an account there,
publishing is easy:
@@ -431,7 +431,7 @@ exist yet then Clojars will automatically create it and give you
For further details about publishing including setting up private
-repositories, see the [deploy guide](
+repositories, see the [deploy guide](
## That's It!

0 comments on commit 2cb7ec9

Please sign in to comment.