Clojurians Log v2

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

seems dubious to me :)

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 -->
    </plugins>
    <build>
      <sourceDirectory>src/main/clojure</sourceDirectory>
    </build>
  </build>
</project>

what version are you on?

there have been bugs and fixes on this

clj -Sdescribe

"1.10.1.561"

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)

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

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

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

I prefer "prerelease" to "unstable" :)

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

brew install clojure/tools/clojure@1.10.1.561
brew link --overwrite clojure@1.10.1.561

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: https://github.com/borkdude/clj-kondo/issues/945