Fork me on GitHub
Alex Miller (Clojure team)02:09:10

clj (prerelease) is now available: • Classpath ordering changes. Classpath will always now be ordered extra-paths, paths, then libs. Libs are ordered by tree depth, then alpha. These changes both revert some ordering changes in the last stable release and go further in defining a reproducible classpath order. • clj -Stree re-enabled for now while we decide on best way to convey classpath-changing options to -Stree and -Spom • Windows scripts updated to latest • This prerelease version should be considered a release candidate for the next stable version! If you try it and have feedback, please leave it here


@alexmiller I assume the -Stree restoration is because of this difference?

seanc@DESKTOP-QU2UJ1N:/var/www/honeysql$ clojure -Stree
org.clojure/clojure 1.10.1
  org.clojure/spec.alpha 0.2.176
  org.clojure/core.specs.alpha 0.2.44
seanc@DESKTOP-QU2UJ1N:/var/www/honeysql$ clojure -X:deps tree
org.clojure/clojure 1.10.1
  org.clojure/core.specs.alpha 0.2.44
  org.clojure/spec.alpha 0.2.176
org.clojure/tools.deps.alpha 0.9.799
  javax.inject/javax.inject 1 0.8.408
    org.clojure/data.json 0.2.7
    commons-codec/commons-codec 1.13
    ... lots more stuff ...

Alex Miller (Clojure team)04:09:46

yes, but that's just a symptom of the greater problem, which is how to convey classpath changing arguments to tools like pom and tree without doing it through clj's args

Alex Miller (Clojure team)04:09:18

Datomic's ion-dev has the same need (for lib bundling)

Alex Miller (Clojure team)04:09:44

so we're looking at something common for all these but don't want to gate on figuring that out

Alex Miller (Clojure team)04:09:29

The -X:deps tree stuff is going to have more features over time for other variants of viewing the tree etc


Interesting. Thanks, Alex.


I thought that the corfield comma was documented on but it seems not. Is it documented on the site somewhere? It would be useful for the docs to link to as it is tripping users up.


in #parinfer we were talking about use of the comma recently for a variety of things:


how do people handle bumping the version inside pom.xml with minimal effort?


i'm not beneath sed but I was hoping for something intelligent

Alex Miller (Clojure team)19:09:19

I've done manual, various Maven plugins, sed

Alex Miller (Clojure team)19:09:49

the contrib projects actually have this done automatically via Jenkins Maven integration


I edit it manually as the last step of preparing for a release -- and I edit both the <version> and the <tag> entries to be consistent (the latter just has v at the beginning). I tend to do a global find for a regex that captures the current release, the new (planned) release, and my generic placeholder (e.g., which I may tag new functionality with in the readme, docs, code, and change log. Then I just work my way through those find results one at a time, and I can eyeball that all matches correctly refer to the new release and the old release as needed.


(so I might search for 1\.\1.(next|588|623) for example)


Ugh, why not just create pom.xml from some tdeps-generated inputs?


Bumping the version will be a different arg to a pom-generating fn


@ghadi is included in bb, I've done XML rewriting with that


(here's a script for getting the version out of a pom.xml:

😎 3

makejack updates the pom based on a :version tag in a project.edn file. I haven’t got a task to bump the version yet.


sed it is

Alex Miller (Clojure team)20:09:38

in case it saves you any time... (made for Mac sed)