Skip to content

Commit c12ea0c

Browse files
committed
add api doc links
1 parent 1e08b6c commit c12ea0c

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

content/reference/clojure_cli.adoc

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -667,7 +667,7 @@ Print the docstrings for the help namespace itself (note that `help` is defined
667667
clojure -X:deps help/doc :ns help
668668
----
669669

670-
* Also see: https://clojure.github.io/tools.deps.cli/clojure.tools.deps.cli.help-api.html[API docs]
670+
See: https://clojure.github.io/tools.deps.cli/clojure.tools.deps.cli.help-api.html[API docs]
671671

672672
[[deps_prep]]
673673
=== Prep libs
@@ -702,7 +702,7 @@ To find and "prepare" libs in the dependency tree you can use the `prep` tool pr
702702
clj -X:deps prep
703703
----
704704

705-
The prep task will find all libs in the dependency expansion and look for libs that are source libs, need prep (based on their `:deps/prep-lib` key), and are not yet prepped (based on the `:ensure` dir in their `:deps/prep-lib` map). Those libs will run the command specified there by alias and function, as if: `clj -T:<alias> <fn>`.
705+
The https://clojure.github.io/tools.deps.cli/clojure.tools.deps.cli.api-api.html#clojure.tools.deps.cli.api/prep[prep] task will find all libs in the dependency expansion and look for libs that are source libs, need prep (based on their `:deps/prep-lib` key), and are not yet prepped (based on the `:ensure` dir in their `:deps/prep-lib` map). Those libs will run the command specified there by alias and function, as if: `clj -T:<alias> <fn>`.
706706

707707
Once a library has been prepped, it does not need to be prepped again by other users of this git library version.
708708

@@ -711,6 +711,8 @@ Once a library has been prepped, it does not need to be prepped again by other u
711711
Should you use a prep step that compiles your Clojure code? Generally, no. All users of this git library on a machine will share the prepared classpath created by the prep step. The choice of Clojure compiler and dependent libraries is better left to each application making using of this lib. For more on using dev-time compilation, see the <<xref/../../guides/dev_startup_time#,Dev Startup Time>> guide.
712712
====
713713

714+
See: https://clojure.github.io/tools.deps.cli/clojure.tools.deps.cli.api-api.html#clojure.tools.deps.cli.api/prep[API doc]
715+
714716
[[deps_find_versions]]
715717
=== Find versions
716718

@@ -728,6 +730,8 @@ The params that can be provided are:
728730

729731
`find-versions` will print the git or Maven coordinates, one per line, to the console.
730732

733+
See: https://clojure.github.io/tools.deps.cli/clojure.tools.deps.cli.api-api.html#clojure.tools.deps.cli.api/find-versions[API doc]
734+
731735
[[deps_mvn_install]]
732736
=== Local Maven install
733737

@@ -763,17 +767,16 @@ As mentioned above, edn strings must be in double quotes, and then single-quoted
763767

764768
A pom file must be either provided explicitly, generated from :lib/:version, or found inside the .jar file (the default).
765769

770+
See: https://clojure.github.io/tools.deps.cli/clojure.tools.deps.cli.api-api.html#clojure.tools.deps.cli.api/mvn-install[API doc]
771+
766772
[[deps_mvn_pom]]
767773
=== Generate Maven pom
768774

769775
Use the following program to generate or update an existing pom.xml with the deps and paths from your project:
770776

771777
* `-X:deps mvn-pom` - generate (or update an existing) pom.xml with deps and paths
772778

773-
See https://clojure.github.io/tools.deps.cli/clojure.tools.deps.cli.api-api.html#clojure.tools.deps.cli.api/mvn-pom[API docs] for more.
774-
775-
776-
779+
See: https://clojure.github.io/tools.deps.cli/clojure.tools.deps.cli.api-api.html#clojure.tools.deps.cli.api/mvn-pom[API doc]
777780

778781
[[tools]]
779782
== Tools

0 commit comments

Comments
 (0)