This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-26
Channels
- # aleph (5)
- # announcements (16)
- # babashka (36)
- # beginners (161)
- # calva (24)
- # cider (8)
- # circleci (45)
- # clj-kondo (5)
- # cljs-dev (25)
- # cljsrn (5)
- # clojure (116)
- # clojure-europe (10)
- # clojure-nl (18)
- # clojure-uk (14)
- # clojuredesign-podcast (6)
- # clojurescript (50)
- # cursive (12)
- # data-science (8)
- # datomic (8)
- # duct (39)
- # emacs (6)
- # fulcro (21)
- # graalvm (12)
- # kaocha (17)
- # off-topic (184)
- # pathom (1)
- # pedestal (2)
- # re-frame (31)
- # reagent (24)
- # reitit (1)
- # sci (1)
- # shadow-cljs (23)
- # sql (147)
- # tools-deps (8)
- # vrac (3)
- # xtdb (35)
Trying out Cursive, I’m having a somewhat weird error to do with package resolution
Errors during project resolution
The following errors were found during project resolve:
/Users/ ... /deps.edn:
/.m2/repository/buddy/buddy-core/1.6.0/buddy-core-1.6.0.pom.part.lock (No such file or directory)
It works perfectly fine on linux, but running on MacOS gets stuck on this.
I’m also getting the “no modules containing clojure.main found” error when trying to set up a run configuration.
Happens with both local tools and using tools.deps directly.
As something possibly related, my deps aliases don’t appear to be working. Source paths from aliases I’ve apparently included don’t appear to have any effect.That package error is very weird. Do you get that using deps on the command line in that package?
The “No modules…” error is probably because your project didn’t sync correctly due to the first error.
Aliases will need to be configured like this: https://cursive-ide.com/userguide/deps.html#working-with-aliases
It works fine running with deps, it’s just cursive/intellij that seems to be having the issue
> /.m2/repository/buddy/buddy-core/1.6.0/buddy-core-1.6.0.pom.part.lock (No such file or directory)
unless you redacted some portions of the path above, it indicates that the .m2
directory is under the /
(root) directory (it's usually under ~
, i.e., the path should have been something like ~/.m2/repository/buddy/buddy-core/1.6.0/buddy-core-1.6.0.pom.part.lock
) and whatever process that's resolving the maven artifacts is having access permission issues with that directory.