This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-02
Channels
- # 100-days-of-code (1)
- # announcements (2)
- # beginners (122)
- # boot (5)
- # calva (5)
- # cider (54)
- # cljdoc (1)
- # clojure (132)
- # clojure-brasil (1)
- # clojure-italy (4)
- # clojure-nl (6)
- # clojure-uk (105)
- # clojurescript (43)
- # core-async (17)
- # cursive (14)
- # datomic (60)
- # emacs (35)
- # figwheel-main (44)
- # fulcro (70)
- # graphql (1)
- # jobs (19)
- # jobs-discuss (5)
- # leiningen (5)
- # luminus (2)
- # off-topic (40)
- # onyx (2)
- # overtone (5)
- # re-frame (36)
- # reagent (29)
- # ring-swagger (20)
- # rum (13)
- # shadow-cljs (19)
- # testing (5)
- # tools-deps (25)
- # vim (5)
is there a way to figure out in a clojure process started with clj which aliases were used to start it?
The aliases are only used to build the classpath (and main opts etc). By the time your program is running, none of that is available.
What is the problem you're trying to solve here?
Iām looking into a solution for this cider issue: https://github.com/clojure-emacs/cider/issues/2308#issuecomment-426029865
cider checks if dependencies for certain functionality are on the classpath. until now, simply by splitting the classpath entries and interpreting that. this falls apart when using tools.deps git and local coordinates
Yup. Well, I think CIDER is trying to be far too clever here and making all sorts of unwarranted assumptions -- but it sounds like Bozihdar is aware of the problem and will figure it out -- he's been doing amazing stuff with CIDER...
clj
and tools.deps
are making a lot of people reconsider their assumptions š
The safe way to do it is to check for the existence of namespaces/classes, not to search the classpath for them.
@seancorfield @alexmiller I have a simple repro (on my machine) - from a clean install. Unzip the .zip file into an empty directory and run clj -A:uberjar -Srepro -Sforce
- would any of you be so kind as to confirm / invalidate the repro so I can make a formal issue?
FYI the repro sequence was: with an empty /.m2, /.clojure on OS X high sierra with brew install clojure
, `clj -Sdeps '{:deps
{seancorfield/clj-new
{:git/url "https://github.com/seancorfield/clj-new"
:sha "21ca1b27f46dc324be084ba839beca555aeda387"}}}' \
-m clj-new.create \
app \
krukow/artifact-exception` and then clj -A:uberjar -Srepro -Sforce
in the folder where simple-repro.zip
is unzipped.
FYI: posting this to https://github.com/luchiniatwork/cambada/issues
Ouch! That's quite the gotcha!
@dominicm I think that's correct! I'll add to: https://github.com/luchiniatwork/cambada/issues/15
One more general question: where can I find the source code for the clojure & clj CLI tools
The brew-install
and tools.deps.alpha
repos under the clojure
org.
(the former is the shell scripts etc, the latter is the library they use for all the dependency stuff)
@krukow this PR should fix the issue you were having https://github.com/luchiniatwork/cambada/pull/14