Clojurians Log v2

Working through perun's Getting Started, I'm getting an "java.lang.IllegalArgumentException: No such task (markdown)" at the boot markdown step. It appears true: boot is installed, but does not seem to have a markdown task. I'm investigating whether this is due to a boot version mismatch (2.5.2 from brew versus 2.5.5 in the properties file) but just FYI.

@daveliepmann: hey there :simple_smile: what does your build.boot look/cli invocation look like?

@daveliepmann: just out of curiousity, what's the expectation about what you'll walk away with after finishing the getting started?

build.boot is straight out of the box: `(set-env! :source-paths #{"src" "content"} :dependencies '[ [perun "0.3.0" :scope "test"] ]) (require '[io.perun :refer :all]) `

@martinklepsch: expectations? I suppose a bare-bones static site running on localhost

from markdown to html

cool.

if you run boot -V it should show BOOT_VERSION being 2.5.5 no matter if you isntalled 2.5.2 from homebrew. the thing you get from homebrew is only a minimal shim

roger—`boot -V` returns 2.5.5

thanks for jumping in, you're everywhere :simple_smile:

only other explanation I have for what you describe above is that you're not in the directory where that build boot is haha

you might want to try boot -s src -s content -d perun markdown which is essentially the same as that build.boot

@daveliepmann: I'm happy to. I think perun is pretty cool but still quite unfriendly towards beginners so I'm trying to make up for that :simple_smile:

beginners as in both, programming and/or perun beginners

@martinklepsch: yeah, you got it—in the midst of switching from eshell to terminal I found myself in the root directory instead of in the project. Thanks!

but then, was I using 2.5.2 in the root?

@daveliepmann: not sure I understand that Q, if you didn't run boot in the directory that hat the boot.properties file you might get another version of boot

I'm saying that since I ran boot -V (and got 2.5.5) from the same directory (without boot.properties) that I tried to run boot markdown in, I see two possibilities: either the boot version isn't the problem or it's reporting the wrong version of boot while I'm in that (wrong) directory

> either the boot version isn't the problem the problem causing what other problem? I'm confused 😅

sorry, I know I'm off script :simple_smile:

It's a bit academic and I'm not familiar with boot internals so this may not be a productive line of questioning

@martinklepsch: anyway thanks for helping me back on track. Cheers!

@daveliepmann: sure, let me know if you have any more questions or suggestions.

Also if you see anything that could be improved, it's a wiki :simple_smile: