Fork me on GitHub
Matti Uusitalo07:10:03

Is there a clojure version requirement specified somewhere? I ran into some problems running clojure 1.10.0 when the examples in readme didn’t work. After upgrading it worked fine.


@matti.uusitalo Can you be a bit more specific about "some problems"? I've tested depstar on Clojure 1.7 right up to Clojure 1.10.2-alpha2 and it seemed fine.

Matti Uusitalo03:10:28

Sure. Sorry about being so vague. I added this to my deps.edn:

:aliases {:depstar
            {seancorfield/depstar {:mvn/version "1.1.128"}}}}
Then I used this command to build the uberjar
clojure -M:depstar -m hf.depstar.uberjar TilapalvelutApi.jar -C -m tilapalvelut-api.main
What I got was
Exception in thread "main" Could not locate hf/depstar/uberjar__init.class, hf/depstar/uberjar.clj or hf/depstar/uberjar.cljc o
n classpath.          

Matti Uusitalo03:10:05

However, after upgrading Clojure version it worked.

Matti Uusitalo03:10:44

Maybe it’s the command line arguments.

Matti Uusitalo03:10:47

Someone mentioned I should have used -A instead of -M


@matti.uusitalo Yeah, the -M option hadn't used to bring in extra deps etc, whereas it does in the new CLI.


-A still runs main opts but it won't at some point -- so using -M now you've upgraded the CLI is the right approach.


I'll update the depstar README to make that clear.

Matti Uusitalo03:10:12

Thanks! I was really confused why it wouldn’t work. In hindsight I probably should have looked at the CLI documentation to find out why.


There are lots of changes between the and versions of the CLI tools.


Nah, my fault. I remembered to update the README with a note about the version. I forgot to update depstar.

Matti Uusitalo03:10:30

Well, I wouldn’t lay blame on you. After all you’re maintaining a great tool that the community can use for free.

Matti Uusitalo03:10:22

actually many great tools to be exact


Yeah, but I'm the one who updated those READMEs to use options that no longer work for older CLIs 🙂 I sometimes forgot that not everyone stays on the bleeding edge like I do (we already have on our production servers I think and on our dev/QA systems -- and we're running Clojure 1.10.2-alpha2 in production).