Do appreciate your response, better than I hoped for, will digest it and
take into consideration.
The goal is not vanity, but creating value, so mult is not a rush to prove
oneself.
Will take all the critique and comments and seriously think whether or not
mult brings value. If not, I won't was
Ok, let's reset as we start talking about different things now.
None of these libraries are broken. They just include resources. Also, I
don't think it is realistic to tell library authors to please move certain
files out of the way because my build tool randomizes my classpath. That is
not goi
FYI, I've been working with the homebrew team today and homebrew-core now
points to the latest stable clojure tools version and will track that
automatically going forward.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send
On Tue, Aug 11, 2020 at 6:41 PM 'bed...@yahoo.com' via Clojure <
clojure@googlegroups.com> wrote:
> Just 2 quick points before I go back to migrate to shadow-cljs & leiningen
> ;)
>
> "just does not seem well defined "
> This is not a line of argument you want to pursue when we are talking
> about
Can you change that resources file and see if what you're looking at
changes to double check? I did actually check a bunch of jars from the
prior message and did some searching for that message. Or you could even
dump the classpath with -Spath, then move resources to the front, then use
-Scp (which
Just 2 quick points before I go back to migrate to shadow-cljs & leiningen
;)
"just does not seem well defined "
This is not a line of argument you want to pursue when we are talking about
maven, who has had a stable order for what feels like decades now.
If you need a current link:
https://mav
Hi - I just tried your suggestion and no joy:
~/work/tmp810/xanadu > clj -e "((requiring-resolve '
clojure.java.io/resource) \"public/index.html\")"
DEPRECATED: Libs must be qualified, change deps-ancient =>
deps-ancient/deps-ancient (deps.edn)
DEPRECATED: Libs must be qualified, change reagent
On Tue, Aug 11, 2020 at 3:01 PM 'bed...@yahoo.com' via Clojure <
clojure@googlegroups.com> wrote:
> Here's some maven-specific discussion:
> https://stackoverflow.com/questions/793054/maven-classpath-order-issue.
> They have a defined order since 2.0.9. and declaration order is considered
> for tr
Here's some maven-specific discussion:
https://stackoverflow.com/questions/793054/maven-classpath-order-issue.
They have a defined order since 2.0.9. and declaration order is considered
for transitive dependencies conflict.
Intellij's Dependencies tab in Module settings: You can re-order the
de
Just to beat the horse...
On Tue, Aug 11, 2020 at 1:05 PM 'bed...@yahoo.com' via Clojure <
clojure@googlegroups.com> wrote:
> Changing the order of classpath entry and not having paths be at the
> beginning of the CLASSPATH will break existing code that uses `(io/resource
> ...)` to load resource
Changing the order of classpath entry and not having paths be at the
beginning of the CLASSPATH will break existing code that uses `(io/resource
...)` to load resources from the CLASSPATH.
While in theory the order of the classpath should not matter, in practice
it does, often involuntarily.
Fig
This might be a good incentive for people to keep their published .jar
files clean. Unfortunately many published CLJS libs contain the rather
common "public" folder with "public/index.html" and often compiled .js
artifacts which aren't actually ever used.
I do however think that it is useful to
Looks super interesting! Some quick thoughts/questions:
Why is it a goal to write an editor in Clojure? Would this editor be a
general one, or would it be a Clojure editor?
I am of course happy you see Calva as a good option for Clojure coding. I
think the major thing lacking from it is Socket RE
13 matches
Mail list logo
