Okay, I have a clojure project, I have run

lein uberjar

However, running the jar with

java -jar (the anme of the jar) 

I have tried it now with a print outside of main, and that print goes off, but nothing in main does...

does it work if you do "lein run"?

Hm, the instructions here worked for me on a new project - https://github.com/technomancy/leiningen/blob/master/doc/TUTORIAL.md#uberjar

those are the instructions I followed.

Lein run hits the print in the namespace, but none of the prints in main

can you share the code? In particular, the signature of -main, the namespace, and the configuration in project.clj?

one sec

you’re running the standalone jar, yes?

This is for a class project, so it's really simple. Hence frustrating when it does not work

(ns lab1.core
  (:gen-class))

---code here---

(println "Hello")
(defn -main [& args]
  (let [n (inc (Integer/parseInt (first args)))]
   (handle-recursion [] (vec (range 1 n)))))

(defproject lab1
  :main lab1.core
  :aot [lab1.core])

looks sensible. Just checking - what happens if you put (println "Hello") as the first line in -main and recompile the uberjar?

I just don’t know what the implementation of handle-recursion does - is that going to print something?

Yes. It, prints a lot.

Just wonder if maybe there is lazyness in that function

Oh...

As a guess, it’s maybe because your print statement is at the top level of the namespace rather than in a function?

that could be a thing, one moment

Just wondering if you put a basic println inside the -main, that would help conform if the issue is with the -main or with the handle-recursion function.

conform->confirm

yep, i put a print in, before the let block, and it printed from there

cool, then my guess is lazyiness. Can you wrap in a doall?

doall

Gotcha. Can you share the source for handle-recursion?

okay.

putting it in a paste so that the lab solution does not become public

https://pastebin.com/fedxieK5

cool

aside from the already given ns and main, that is the whole file

thx

looking now

Thank you both, @bbrinck and @rsslldnphy

Also, feel free to bounce me over to #leiningen

@shawx538 no, it’s fine. I think the issue is with the implementation of handle-recursion, not necessarily with lein, but just confirming now

Basically, it looks to me like handle-recursion is using lazy sequences but also trying to do effects (namely println). I’m not immediately seeing why doall isn’t helping here - probably I’m missing something.

Nonetheless, I think a good solution would be to make handle-recursion just return the results as data, then print them out in -main. I’ll see if I can come up with an example

I'll hammer at it too. That is more functional, we just also did not want to have handle-recursion ever have to hold the full return in memory

@shawx538 Hm, I wonder if lazy-seq might be a good fit here if you want to avoid having everything in memory https://clojuredocs.org/clojure.core/lazy-seq

(untested)

@shawx538 can I DM you my workaround for the printing issue?

(since you mentioned keeping it hidden since it’s a lab)

yes, that would be good

OK, sent. Good luck!

@shawx538 Since you're brand new to Clojure, you will find #beginners to be a good place to ask questions. Folks there have opted in to helping beginners with these sorts of questions. Folks are very patient and helpful in that channel. (I'm one of the moderators her, BTW)

I know, I admire your expectations library, and use it in my own projects. Sorry if this was in the wrong channel.

Thanks 🙂 Re: the channel -- not wrong, and out of "mainstream" office hours it's fine, just trying to set expectations for where you'll get the best help for that sort of question...

hello! anyone have some examples of using clj-camel library? i'm facing some issues to understand how to make use of things like getting/setting values to pass along the pipeline...

for exemple, how to get the exchange object from one step to set the body over the next step

Why is there a seperate datatype clojure.lang.Conswhen clojure.lang.PersistentListalready exist. Is there a reason for this design decision in clojure?

A very nice explanation for the above https://gist.github.com/finalfantasia/b20a2a2d3a3ac445e456fbbf2db38cae

I’m doing a presentation for a Clojure meetup, and I’d like to demo CLI deps. However, most of my work has been based on leiningen and Luminus (for web apps). Would it be simple to spin up a REST backend using CLI deps only, that would be suitable for a demo?

it should be reasonable as long as you can spin up your webserver without using a lein plugin (just invoking a -main that starts the server)

as it should be 😉

many people use lein-ring to run for convenience

Java 11 is out, but Clj still on Java 10 or lower due to https://dev.clojure.org/jira/browse/CRRBV-18 😞

Clojure works fine on Java 11 @mike1452 - that issue is for a library

@mike1452 I actually just looked into this the other day, because rrb-vector was available from my repl despite it not being a part of core that ships with clojure by default. turns out it's a dependency of fipp, which in turn is a dependency of cider-nrepl

though since rrb-vector IS a part of core, albeit not one that ships by default, it should probably still be updated

@ghadi thanks. I need to check deps... Oh, it seems that fipp dependency throws this exception

"part of core" in what sense?

@jesse.wertheim thanks.

yeah anything that pulls in RRB vector will be affected -- just need an upstream release of that library

@hiredman as in it's on the clojure.core namespace and maintained under https://github.com/clojure/core.rrb-vector , so I dunno if you only count things if they're shipping with clojure, but I'd say it counts the same way core.async does, no?

it's not part of "core", but a library

same with core.async

the historical definition is core is what ships with the clojure runtime (more or less, spec kind of blurs that a little)

fair enough! seems like you could describe it either way without technically being wrong but I do see the importance of the distinction for obvious reasons

yeah either way it should get fixed stat

it's already fixed upstream, just needs a release cut

@bbloom Java 11 is out! Waiting for fipp update. Thanks 🙂

looks like that lib stagnated a bit before getting some recent love

the funny thing is it just came up in here the other day

@jesse.wertheim @mike1452 Michal just cut a release for core.rrb-vector 0.0.12 - if you put that in your top level dependencies, it should get you going on JDK 11

fipp can update at the maintainer's leisure

is it possible to get meta data from a multimethod implementation?

@ghadi Is it correct artifact? quantum/org.clojure.core.rrb-vector {:mvn/version "0.0.12"}

no

any official clojure build has org.clojure as the group id

quantum/org.clojure.core.rrb-vector is some random person's fork

@hiredman there is no org.clojure/core.rrb-vector in repos

ver 0.0.12

right, that person made a random fork and released their own patch version

the new 0.0.12 version of the official release was just pushed to sonatype's oss repo, and I dunno what the lag might be between the push and becoming available

https://search.maven.org/artifact/org.clojure/core.rrb-vector/0.0.11/jar (no 0.0.12 there yet)

@hiredman Ha! Search still shows 0.0.11. But I put org.clojure/core.rrb-vector 0.0.12 in deps.edn and ta-da...downloaded. Yeah, now my project works under Java 11. Thanks!!!

Hi guys. I searched through the slack but couldn’t find anything. How do you guys deploy your apps? A little background - I’m from non-java world. Tried to dig into it, failed. I figured out there are plenty of options - bare metal (deploy jar), docker, tomcat, wildfly - how do you deploy your apps?

At my company we do java -jar .. inside a docker container on Azure

jsvc is good if you need things like restart and control via standard service stuff

https://commons.apache.org/proper/commons-daemon/jsvc.html

We pass a jar and topology submitter class to Apache Storm.

^class name, the submitter's in the jar

one useful trick is that often instead of using gen-class you can submit clojure.main as your main, and ask it to find and run your ns -main

also you can have multiple launchable -main methods in one jar (whether you use gen-class or clojure.main, either way)