This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-29
Channels
- # announcements (2)
- # beginners (17)
- # calva (3)
- # cljdoc (3)
- # cljsrn (7)
- # clojure (99)
- # clojure-europe (6)
- # clojurescript (18)
- # clojureverse-ops (2)
- # cryogen (1)
- # cursive (11)
- # datomic (2)
- # duct (6)
- # figwheel-main (2)
- # fulcro (3)
- # graalvm (2)
- # honeysql (1)
- # introduce-yourself (5)
- # leiningen (4)
- # meander (11)
- # membrane (14)
- # practicalli (1)
- # re-frame (4)
- # reagent (5)
- # rum (1)
- # shadow-cljs (17)
- # spacemacs (13)
- # tools-deps (6)
What is the recommended way to version a project that uses tools.deps? I mean: where should the version number be placed? Thanks in advance.
@wactbprot Can you explain what you use the version number for? In the code of the app itself? Just in the pom.xml
file? Something else?
Are you building a library? An application?
For my OSS projects (libraries), I've been using the :version
argument of depstar
to update the pom.xml
file's <version>
and <scm><tag>
fields up until I switched to tools.build
which handles both of those in its write-pom
function, and it computes it automatically based on the git
commit count.
Wow, that's a lot of question marks. In pre tools.build times the answer seems to be: it depends. I write oss for a small team (libs and apps). I distribute the code via git. If I interpret your answer correctly, tools.build fills a gap. Thanks for pointing out this new way.
If the code is on github, folks can depend on it directly from their deps.edn file.