This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-27
Channels
- # announcements (3)
- # babashka (16)
- # beginners (177)
- # calva (102)
- # cider (2)
- # clj-kondo (12)
- # clojars (10)
- # clojure (91)
- # clojure-argentina (3)
- # clojure-australia (5)
- # clojure-europe (16)
- # clojure-nl (1)
- # clojure-uk (10)
- # clojurescript (73)
- # community-development (8)
- # cursive (9)
- # depstar (7)
- # fulcro (5)
- # helix (1)
- # introduce-yourself (1)
- # jobs-discuss (18)
- # lsp (32)
- # luminus (1)
- # malli (2)
- # music (4)
- # off-topic (20)
- # pathom (19)
- # polylith (15)
- # re-frame (4)
- # reagent (6)
- # ring (13)
- # sci (36)
- # shadow-cljs (7)
- # spacemacs (4)
- # sql (3)
- # tools-deps (112)
- # vim (21)
Following this discussion https://github.com/clojars/administration/issues/108, what would you think of the ability to deprecate a group?
My thinking is, if you advice projects to change their groupids, then tooling like antq
will be fooled into thinking that no new versions exist for a given project. When in reality they do, just under a different groupid
So perhaps if possible when fetching a dep under "deprecated" groupid, one would see a warning printed. Or if possible, under a 'pedantic' mode one could get a hard failure
antq
does a pretty good job of spotting that a dependency moved to a new group ID -- I've seen it recommend updates from seancorfield/project
to com.github.seancorfield/project
across versions.
how does that work though? There are many groupIds that a project can possibly be upgraded to (I'd love to cc/ the antq author here... forgot his Slack username which is not liquidz apparently?)
I don't think they're on Slack at all -- but you can always read the source to see how it works 🙂
(! 687)-> cat deps.edn
{:deps {seancorfield/depstar {:mvn/version "2.0.216"}}}
(! 688)-> clojure -M:outdated
| :file | :name | :current | :latest |
|----------+----------------------+----------------------+---------------------------------|
| deps.edn | seancorfield/depstar | seancorfield/depstar | com.github.seancorfield/depstar |
It spots the updated group ID.and then you update the group and run it again:
(! 690)-> clojure -M:outdated
| :file | :name | :current | :latest |
|----------+---------------------------------+----------+---------|
| deps.edn | com.github.seancorfield/depstar | 2.0.216 | 2.1.267 |
Available diffs:
-
It does require that a lib was published with the same version under both groups I think...