The warning appears about your own use of unqualified lib names in your
project's dependencies: so it really is "castigating the perpetrator", by
making you use groupId/artifactId format names for dependencies, instead of
the (lazy/convenient) shorthand of artifactId for libs that have a groupId
th
Rich Hickey has pushed using solid domain names before, and I'm super glad
to see more progress on that front. But it's unfortunate if the tools
castigate the victim, not the perpetrator. Wouldn't Clojars be a better
point for enforcement? Has the question been raised with Clojars?
Alex's
Thanks, super helpful. I'll follow-up if I have any questions.
D. Ben Knoble
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patie
Hi, couple things here...
First, for information on this change you can see the section at the very
end of this blog: https://insideclojure.org/2020/07/28/clj-exec/ - probably
best to read that and then I can answer any follow-ups as I tried to
explain there.
Second, this is only in a preview
I've started seeing a lot of messages like this, I think after I updated
clojure, but I can't find any documentation or points in the changelog
about the change, why I'm getting this message, or what the correct fix is.
I know it provides a change I can make, but is it the right one?
Some examp
