Fork me on GitHub

I wonder if there are legal implications when concatenating license texts?

Alex Miller (Clojure team)01:09:28

seems dubious to me :)

☝️ 3

When I run clj -Spom with an existing pom that already has a <build> tag the generated <build> tag is then placed inside of the existing rather than merging the contents or just adding the <sourceDirectory>. Is this a bug or am I just doing it wrong? To be clear, it does this:

<-- Contents above elided -->

Alex Miller (Clojure team)14:09:06

what version are you on?

Alex Miller (Clojure team)14:09:27

there have been bugs and fixes on this

Alex Miller (Clojure team)14:09:14

yeah, that's the newest stable but the fix is not included in a newer stable version yet (it's fixed in the prereleases but you'll get a bunch of other changes with that)

Alex Miller (Clojure team)14:09:05

so you could move to a prerelease ( is newest) or you could fall back to a prior stable version - or earlier

Alex Miller (Clojure team)14:09:41

that version was actually also broken but only for -Spom generating a new pom

Alex Miller (Clojure team)14:09:11

or you can wait till the next stable version, hopefully coming within the next week


or generate the pom with the newest unstable and then move back to the newest stable :)


it's pretty easy to do this if you download the clojure shell script for a given release

Alex Miller (Clojure team)14:09:10

I prefer "prerelease" to "unstable" :)

❤️ 3

@markbastian if you're on mac, this is how you can switch versions easily:

brew install clojure/tools/[email protected]
brew link --overwrite [email protected]


or if you're using linuxbrew, same


Cool, thanks for the help. Waiting for next week is great. I don't need to update the pom much.


Would it be useful if clj-kondo did some checking on deps.edn (statically) for common mistakes? Feel free to post ideas here: