regenerate site

Author: seancorfield

articles/cookbooks/cli_build_projects/index.html

@@ -148,7 +148,7 @@ <h2 id="toolsbuild-and-the-clojure-cli"><code>tools.build</code> and the Clojure
  :aliases
  {
   ;; add this to :aliases in deps.edn:
-  :build {:deps {io.github.clojure/tools.build {:mvn/version "0.10.4"}}
+  :build {:deps {io.github.clojure/tools.build {:mvn/version "0.10.6"}}
           :ns-default build}
  }}
 </code></pre><p>The <code>-T</code> option implicitly sets <code>:paths ["."]</code> (as opposed to <code>:paths ["src"]</code>
@@ -183,7 +183,7 @@ <h2 id="toolsbuild-and-the-clojure-cli"><code>tools.build</code> and the Clojure
                              :main-args ["-e" "(clojure-version)"]})]
     (b/process cmd)))
 </code></pre><p>We can run this with:</p><pre><code>clojure -T:build run
-</code></pre><p>and we'll see the version of Clojure we're running: <code>"1.11.4"</code>.</p><p><strong>Error Handling</strong></p><p>Since we will generally want the build to fail if the command exits with
+</code></pre><p>and we'll see the version of Clojure we're running, for example: <code>"1.12.0"</code>.</p><p><strong>Error Handling</strong></p><p>Since we will generally want the build to fail if the command exits with
 a non-zero status, we'll check the return value of <code>b/process</code> and throw
 an exception if the exit status is non-zero:</p><pre><code class="clojure">    (when-not (zero? (:exit (b/process cmd)))
       (throw (ex-info (str "run failed for " aliases) opts)))
@@ -243,11 +243,12 @@ <h2 id="toolsbuild-and-the-clojure-cli"><code>tools.build</code> and the Clojure
 new <code>test-multi</code> function in <code>build.clj</code>.</p><p>Add these aliases to <code>deps.edn</code>:</p><pre><code class="clojure">  :1.9  {:override-deps {org.clojure/clojure {:mvn/version "1.9.0"}}}
   :1.10 {:override-deps {org.clojure/clojure {:mvn/version "1.10.3"}}}
   :1.11 {:override-deps {org.clojure/clojure {:mvn/version "1.11.4"}}}
+  :1.12 {:override-deps {org.clojure/clojure {:mvn/version "1.12.0"}}}
 </code></pre><p>When these aliases are used in combination with other aliases, the default
 version of Clojure will be overridden with the specified version. We can see
 this by running <code>clojure -T:build run :aliases '[:1.9]'</code> and seeing <code>"1.9.0"</code>
 for example.</p><p>Here's our <code>test-multi</code> function:</p><pre><code class="clojure">(defn test-multi [opts]
-  (doseq [v [:1.9 :1.10 :1.11]]
+  (doseq [v [:1.9 :1.10 :1.11 :1.12]]
     (println "\nTest with Clojure" v)
     (test (update opts :aliases conj v)))
   opts)
@@ -285,6 +286,16 @@ <h2 id="toolsbuild-and-the-clojure-cli"><code>tools.build</code> and the Clojure
 Testing example-test
 1.11.4
 
+Ran 1 tests containing 1 assertions.
+0 failures, 0 errors.
+
+Test with Clojure :1.12
+
+Running tests in #{"test"}
+
+Testing example-test
+1.12.0
+
 Ran 1 tests containing 1 assertions.
 0 failures, 0 errors.
 </code></pre><h2 id="tips-for-building-jar-files">Tips for Building JAR Files</h2><p>Although the official <code>tools.build</code> has examples for
@@ -360,7 +371,7 @@ <h2 id="toolsbuild-and-the-clojure-cli"><code>tools.build</code> and the Clojure
     &lt;dependency&gt;
       &lt;groupId&gt;org.clojure&lt;/groupId&gt;
       &lt;artifactId&gt;clojure&lt;/artifactId&gt;
-      &lt;version&gt;1.11.4&lt;/version&gt;
+      &lt;version&gt;1.12.0&lt;/version&gt;
     &lt;/dependency&gt;
   &lt;/dependencies&gt;
   &lt;repositories&gt;

articles/cookbooks/date_and_time/index.html

@@ -6,10 +6,10 @@
 
 
 <meta name="description" content="This cookbook covers working with Java&#39;s java.time package in two styles, the
-first with interop and the second using libraries.This guide covers Clojure 1.11.4 and Java 8 or later.">
+first with interop and the second using libraries.This guide covers Clojure 1.12.0 and Java 8 or later.">
 
 <meta property="og:description" content="This cookbook covers working with Java&#39;s java.time package in two styles, the
-first with interop and the second using libraries.This guide covers Clojure 1.11.4 and Java 8 or later.">
+first with interop and the second using libraries.This guide covers Clojure 1.12.0 and Java 8 or later.">
 
 <meta property="og:url" content="https://clojure-doc.org/articles/cookbooks/date_and_time/" />
 <meta property="og:title" content="Date and Time" />
@@ -65,7 +65,7 @@ <h2>Date and Time</h2>
     </div>
 
     <p>This cookbook covers working with Java's <code>java.time</code> package in two styles, the
-first with interop and the second using libraries.</p><p>This guide covers Clojure 1.11.4 and Java 8 or later.</p><p>This work is licensed under a <a rel="license" href="https://creativecommons.org/licenses/by/3.0/">Creative Commons Attribution
+first with interop and the second using libraries.</p><p>This guide covers Clojure 1.12.0 and Java 8 or later.</p><p>This work is licensed under a <a rel="license" href="https://creativecommons.org/licenses/by/3.0/">Creative Commons Attribution
 3.0 Unported License</a> (including images &amp; stylesheets). The source is
 available <a href="https://github.com/clojure-doc/clojure-doc.github.io">on Github</a>.</p><h1 id="introduction">Introduction</h1><p>This cookbook does not assume a background in Java, if you have such a
 background the interop section might be of interest.</p><p>This cookbook will be useful if you got your Clojure environment setup, know
@@ -75,7 +75,7 @@ <h2>Date and Time</h2>
 literal</a> is used
 to represent a <code>java.util.Date</code> object.</li></ul><p>While in JavaScript:
 TBD</p><h2 id="libraries">Libraries</h2><ul><li><a href="https://github.com/dm3/clojure.java-time">clojure.java-time</a><blockquote><p>A Clojure wrapper for Java 8 Date-Time API.</p></blockquote></li><li><a href="https://github.com/henryw374/cljc.java-time">cljc.java-time</a><blockquote><p>A Clojure(Script) library which mirrors the java.time api through kebab-case-named vars.</p></blockquote></li><li><a href="https://github.com/juxt/tick">tick</a><blockquote><p>A Clojure(Script) &amp; babashka library for dealing with time. Intended as a replacement for clj-time.</p></blockquote></li></ul><h1 id="preliminaries">Preliminaries</h1><p>The examples below assume the following <code>deps.edn</code></p><pre><code class="clojure">{:paths ["src"]
- :deps {org.clojure/clojure {:mvn/version "1.11.4"}
+ :deps {org.clojure/clojure {:mvn/version "1.12.0"}
         clojure.java-time/clojure.java-time {:mvn/version "1.3.0"}
         com.widdindustries/cljc.java-time {:mvn/version "0.1.21"}}}
 </code></pre><h1 id="recipes">Recipes</h1><h2 id="clojurejava-time"><code>clojure.java-time</code></h2><h3 id="basics">Basics</h3><p>For the people coming from a non-Java background, we are creating an <em>instance</em>

articles/cookbooks/parsing_xml_with_zippers/index.html

@@ -84,7 +84,7 @@ <h2>Parsing XML in Clojure</h2>
   :url ""
   :license {:name "Eclipse Public License"
             :url "https://www.eclipse.org/legal/epl-v10.html"}
-  :dependencies [[org.clojure/clojure "1.11.4"]
+  :dependencies [[org.clojure/clojure "1.12.0"]
                  [org.clojure/data.zip "1.0.0"]])
 </code></pre><p>We are including a dependency on
 <a href="https://github.com/clojure/data.zip">clojure.data.zip</a>, which is a

articles/ecosystem/libraries_authoring/index.html

@@ -78,8 +78,8 @@ <h2>Ecosystem: Library Development and Distribution</h2>
 see <code>clojure-example-library</code> in this guide! We will use <code>my-cool-lib</code>
 as the name of the new project we create and publish here, but you
 can use whatever name you want -- just remember to substitute that
-wherever you see <code>my-cool-lib</code> in this guide.</p><p>This guide uses Clojure 1.11 and a recent version of the Clojure CLI
-(at least 1.11.1.1139; current version is 1.11.4.1474 as of August 2024),
+wherever you see <code>my-cool-lib</code> in this guide.</p><p>This guide uses Clojure 1.12 and a recent version of the Clojure CLI
+(at least 1.12.0.1479; current version is 1.12.0.1488 as of December 2024),
 and requires you have <code>git</code>
 installed (though very little familiarity with <code>git</code> is required).</p><blockquote><p>Note: you should always ensure you have an up-to-date version of the Clojure CLI installed! See <a href="https://clojure.org/releases/tools">Tools Releases</a>. Several of the examples here require 1.11.1.1139 or later: <code>clojure -version</code> should tell you the version you have installed.</p></blockquote><p>It's assumed that you're already somewhat familiar with Clojure. If
 not, see the <a href="/articles/tutorials/getting_started/">Getting Started</a> and
@@ -217,7 +217,7 @@ <h2>Ecosystem: Library Development and Distribution</h2>
 </code></pre><h2 id="write-tests">Write Tests</h2><p>In <code>test/clojure_example_library/my_cool_lib_test.clj</code>, add tests as needed.
 An example is provided in there to get you started.</p><blockquote><p>Note: the example test created by <code>deps-new</code> fails deliberately in order
 for you to get accustomed to writing tests!</p></blockquote><h2 id="write-code">Write Code</h2><p>Write code to make your tests pass.</p><p>Remember to add a note at the top of each file indicating copyright
-(and the license under which the code is distributed, if applicable).</p><p>For example:</p><pre><code class="clojure">;; copyright (c) 2023 -- Sean Corfield, all rights reserved.
+(and the license under which the code is distributed, if applicable).</p><p>For example:</p><pre><code class="clojure">;; copyright (c) 2024 -- Sean Corfield, all rights reserved.
 </code></pre><h2 id="run-tests">Run Tests</h2><p>In your project dir:</p><pre><code>clojure -M:test -m cognitect.test-runner
 </code></pre><p>or:</p><pre><code>clojure -T:build test
 </code></pre><blockquote><p>Note: if you didn't use <code>deps-new</code> to create your library project, you'll want to add a <code>:test</code> alias that adds <a href="https://github.com/cognitect-labs/test-runner">Cognitect's <code>test-runner</code></a> to your project -- see <a href="https://github.com/cognitect-labs/test-runner#configuration"><strong>Configuration</strong></a> in that project's <code>README</code>. The <code>:test</code> alias <code>deps-new</code> generates does not have <code>:exec-fn</code> or <code>:main-opts</code> because it expects you to run tests via the <code>build.clj</code> file, although you can provide <code>-m cognitect.test-runner</code> on the command-line to run tests directly via the CLI, as shown above.</p></blockquote><h2 id="commit-any-remaining-changes">Commit any remaining changes</h2><p>Before continuing to the next step, make sure all tests pass and

articles/tutorials/basic_web_development/index.html

@@ -80,7 +80,7 @@ <h2>Basic Web Development</h2>
 <a href="/articles/tutorials/introduction/">Introduction</a> guides.</p><p>This work is licensed under a <a rel="license" href="https://creativecommons.org/licenses/by/3.0/">Creative Commons
 Attribution 3.0 Unported License</a> (including images &amp;
 stylesheets). The source is available <a href="https://github.com/clojure-doc/clojure-doc.github.io">on
-Github</a>.</p><p>This guide uses Clojure 1.11.4, as well as current versions of the
+Github</a>.</p><p>This guide uses Clojure 1.12.0, as well as current versions of the
 component libraries noted below.</p><h2 id="conceptual-overview-of-components">Conceptual Overview of Components</h2><p>We'll use four major components (briefly described below) for our
 little webapp:</p><ul><li>Ring</li><li>Compojure</li><li>Hiccup</li><li>H2</li></ul><h3 id="ring">Ring</h3><p><a href="https://github.com/ring-clojure/ring">Ring</a> (<a href="https://clojars.org/ring">at
 clojars</a>) is a foundational Clojure web
@@ -115,8 +115,8 @@ <h2>Basic Web Development</h2>
 file to specify the libraries we want to use, and a couple of folders: one
 for CSS files and one for your source code.</p><p>The <code>deps.edn</code> file should have the following contents:</p><pre><code class="clojure">{:paths ["src" "resources"]
  :deps {;; basic Ring and web server:
-        ring/ring-core {:mvn/version "1.12.2"}
-        ring/ring-jetty-adapter {:mvn/version "1.12.2"}
+        ring/ring-core {:mvn/version "1.13.0"}
+        ring/ring-jetty-adapter {:mvn/version "1.13.0"}
         ;; logging, required by jetty:
         org.slf4j/slf4j-simple {:mvn/version "2.0.13"}
 
@@ -236,7 +236,7 @@ <h2>Basic Web Development</h2>
 the value for that column.</p><p>You can try the code out in the <code>comment</code> form by evaluating each expression
 in it, and you should see the same results as the inline comments show.</p><p>You can also try those calls yourself in a standalone REPL,
 if you like:</p><pre><code class="clojure">clj
-Clojure 1.11.4
+Clojure 1.12.0
 user=&gt; (require 'my-webapp.db)
 nil
 ;; you must require a namespace before you go into it:
@@ -400,12 +400,12 @@ <h2>Basic Web Development</h2>
 <a href="https://clojure.org/guides/tools_build"><code>tools.build</code> guide</a> for more details.</p><p>To make your webapp suitable for deployment, make the following
 changes:</p><h3 id="changes-in-depsedn">Changes in deps.edn</h3><p>In your <code>dep.edn</code> file add the following, after the <code>:deps</code> hash map:</p><pre><code class="clojure"> :aliases
  {;; Run with clj -T:build function-in-build
-  :build {:deps {io.github.clojure/tools.build {:mvn/version "0.10.4"}}
+  :build {:deps {io.github.clojure/tools.build {:mvn/version "0.10.6"}}
           :ns-default build}}
 </code></pre><p>The whole <code>deps.edn</code> file should now look like this:</p><pre><code class="clojure">{:paths ["src" "resources"]
  :deps {;; basic Ring and web server:
-        ring/ring-core {:mvn/version "1.12.2"}
-        ring/ring-jetty-adapter {:mvn/version "1.12.2"}
+        ring/ring-core {:mvn/version "1.13.0"}
+        ring/ring-jetty-adapter {:mvn/version "1.13.0"}
         ;; logging, required by jetty:
         org.slf4j/slf4j-simple {:mvn/version "2.0.13"}
 
@@ -423,7 +423,7 @@ <h2>Basic Web Development</h2>
         com.h2database/h2 {:mvn/version "2.2.224"}}
  :aliases
  {;; Run with clj -T:build function-in-build
-  :build {:deps {io.github.clojure/tools.build {:mvn/version "0.10.4"}}
+  :build {:deps {io.github.clojure/tools.build {:mvn/version "0.10.6"}}
           :ns-default build}}}
 </code></pre><h3 id="add-a-buildclj-file">Add a build.clj file</h3><p>The <code>tools.build</code> library is intended to be used with a <code>build.clj</code> script
 which typically lives in the root of your project and is invoked via the

articles/tutorials/editors/index.html

@@ -6,14 +6,18 @@
 
 
 <meta name="description" content="The last
-&quot;State of the Union&quot; Clojure survey (survey question 20) indicated
-that Emacs is still the most popular editing environment, followed by IntelliJ/Cursive, VS Code, and Vim.If you are already using one of these editors, follow one of the guides for that
+&quot;State of the Union&quot; Clojure survey indicated
+that Emacs is still the most popular editing environment (although it has
+fallen to just under 40%), followed by IntelliJ/Cursive and VS Code
+(equal at 23%), and then Vim (around 12.5%).If you are already using one of these editors, follow one of the guides for that
 editor to integrate a REPL-based Clojure workflow, so that you can focus on
 learning just the language.">
 
 <meta property="og:description" content="The last
-&quot;State of the Union&quot; Clojure survey (survey question 20) indicated
-that Emacs is still the most popular editing environment, followed by IntelliJ/Cursive, VS Code, and Vim.If you are already using one of these editors, follow one of the guides for that
+&quot;State of the Union&quot; Clojure survey indicated
+that Emacs is still the most popular editing environment (although it has
+fallen to just under 40%), followed by IntelliJ/Cursive and VS Code
+(equal at 23%), and then Vim (around 12.5%).If you are already using one of these editors, follow one of the guides for that
 editor to integrate a REPL-based Clojure workflow, so that you can focus on
 learning just the language.">
 
@@ -71,8 +75,10 @@ <h2>Clojure Editors</h2>
     </div>
 
     <p>The last
-<a href="https://clojure.org/news/2023/06/30/state-of-clojure-2023">"State of the Union" Clojure survey</a> (survey question 20) indicated
-that Emacs is still the most popular editing environment, followed by IntelliJ/Cursive, VS Code, and Vim.</p><p>If you are already using one of these editors, follow one of the guides for that
+<a href="https://clojure.org/news/2024/12/02/state-of-clojure-2024">"State of the Union" Clojure survey</a> indicated
+that Emacs is still the most popular editing environment (although it has
+fallen to just under 40%), followed by IntelliJ/Cursive and VS Code
+(equal at 23%), and then Vim (around 12.5%).</p><p>If you are already using one of these editors, follow one of the guides for that
 editor to integrate a REPL-based Clojure workflow, so that you can focus on
 learning just the language.</p><p>If you are not using one of these four editors, try to pick the one that is
 closest to what you are currently using, unless your editor is listed on

articles/tutorials/getting_started/index.html

@@ -98,7 +98,7 @@ <h2>Getting Started</h2>
 repositories) without needing JAR files to be built and deployed.</p><p>Since the release of the official Clojure CLI, usage of Leiningen has dropped
 as the community adopted the new CLI and associated libraries such as
 <code>tools.deps</code> and <code>tools.build</code>.
-<em>[See <a href="https://clojure.org/news/2022/06/02/state-of-clojure-2022">State of Clojure 2022 Survey Results</a> -- and a year later the CLI usage exceeded 70% while Leiningen had dropped to around 60%]</em></p><p><strong>Too Much Information! What Should I Use?</strong></p><p>As noted above, if you're following a book or tutorial that uses Leiningen,
+<em>[See <a href="https://clojure.org/news/2024/12/02/state-of-clojure-2024">State of Clojure 2024 Survey Results</a> -- the CLI usage is just over 76% while Leiningen has dropped below 52%]</em></p><p><strong>Too Much Information! What Should I Use?</strong></p><p>As noted above, if you're following a book or tutorial that uses Leiningen,
 or working with a project that uses Leiningen, then keep using Leiningen.</p><p>If you're following a book or tutorial that uses the newer CLI, or working
 with a project that uses it, then keep using the Clojure CLI and associated
 libraries.</p><p>If you're starting from scratch, learning the Clojure CLI is probably a

articles/tutorials/getting_started_cli/index.html

@@ -80,7 +80,7 @@ <h2>Getting Started with the Clojure CLI</h2>
 see the list of all the options available.</p><h2 id="trying-out-the-repl">Trying out the REPL</h2><p>Once you have the Clojure CLI installed, you can run it from anywhere you like
 to get a REPL:</p><pre><code>$ clj
 </code></pre><p>You should be greeted with the Clojure version and a "<code>user=&gt;</code>" prompt. Try it out:</p><pre><code class="clojure">$ clj
-Clojure 1.11.4
+Clojure 1.12.0
 user=&gt; (+ 1 1)
 ;; ⇒ 2
 user=&gt; (distinct [:a :b :a :c :a :d])
@@ -109,10 +109,10 @@ <h2>Getting Started with the Clojure CLI</h2>
 <code>clojure.main</code> can also evaluate expressions:</p><pre><code>$ clojure -M -e '(println "Hello, Command!")'
 Hello, Command!
 </code></pre><p>or:</p><pre><code>$ clojure -M -e '(clojure-version)'
-"1.11.4"
+"1.12.0"
 </code></pre><p>The <code>-e</code> option prints the value returned by the expression (if it is not <code>nil</code>).</p><blockquote><p>Note: you can find more detailed information about <a href="https://clojure-doc.org/articles/ecosystem/libraries_authoring/#creating-new-projects">Creating New Projects</a> later in this guide.</p></blockquote><h3 id="working-in-the-repl">Working in the REPL</h3><p>In your project directory, start up a repl (<code>clj</code>) and
 run your <code>-main</code> function to see its output in the repl:</p><pre><code>$ clj
-Clojure 1.11.4
+Clojure 1.12.0
 user=&gt; (require 'my.proj)
 nil
 user=&gt; (my.proj/-main)