https://ask.clojure.org/index.php/qa/tools/leiningen https://ask.clojure.org/index.php/13968/using-log4j-layout-template-json-with-leiningen?show=13969#a13969 <p>If you depend on multiple libraries that each have their own plugins cache (the <code>.dat</code> file), you need to merge those as part of your build process -- which is what the <code>log4j2-plugins-cache</code> plugin is for, with Leiningen.</p> <p>In log4j 3.x, they plan to do away with this cache file and use something more amenable to build tooling that doesn't require custom merging like this.</p> <p>I had to write something similar for <code>tools.build</code> / <code>build.clj</code> for use with the Clojure CLI: <a rel="nofollow" href="https://github.com/seancorfield/build-uber-log4j2-handler">https://github.com/seancorfield/build-uber-log4j2-handler</a></p> Leiningen https://ask.clojure.org/index.php/13968/using-log4j-layout-template-json-with-leiningen?show=13969#a13969 Thu, 13 Jun 2024 17:10:43 +0000 https://ask.clojure.org/index.php/13157/problem-with-leiningen-and-a-local-library?show=13161#a13161 <p>Your setup is uncommon, therefore it is kinda hard to figure out what you expect to happen or why you'd want typically development only files in the .jar.</p> <p>In common Clojure(Script) setups libraries only contain their source code, and no compiled artifacts. Actual projects then use those libraries to build what they need.</p> <p>There can still be CLJS builds in the library as well, but those would only be relevant for the development of that library, and not part of the actual published outputs.</p> <p>If for some reason you don't want this and prefer to keep the build in the library, then the only relevant file the project should include in the <code>.jar</code> is the <code>.js</code> file produced by the <code>prod</code> build. Which is likely defined in a <code>prod.edn</code> in the project. It likely only produces one output file. The files you complained about missing are development files, and should no longer be relevant.</p> <p>Your project also seems to be a little stitched together since there are still remnants of what probably used to be <code>lein-cljsbuild</code> config, yet also some newer <code>figwheel.main</code> references. You probably want to clean that up so it is easier to figure out what is actually going on.</p> <p>I'm also not sure about the use of <code>lein-localrepo</code>. A simpler <code>lein install</code> should achieve the same, if the goal is using the local installed library from the project. Not sure what else <code>localrepo</code> does exactly.</p> Leiningen https://ask.clojure.org/index.php/13157/problem-with-leiningen-and-a-local-library?show=13161#a13161 Wed, 16 Aug 2023 08:52:08 +0000