Clojurians Log v2

Anyone else seeing this while running cljdoc locally?

Exception in thread "main" java.lang.Exception: Exception reading CLJDOC_VERSION from classpath, compiling:(telegram.clj:9:11)

This could be due to a recent merge

that file is expected to be on the classpath when you run cljdoc with the production profile

yep, could be was working fine before I pulled the latest.

I put a note in that ticket @martinklepsch, but I've released my pom-updating tool, and I have it generating <scm> tags in the pom.xml. Let me know if it looks useful. https://github.com/workframers/garamond

can you check what (cljdoc.config/profile) returns?

sorry for the trouble 🙂

YES! I already saw & it looks very good. Not sure I have use for the versioning stuff at this point but the pom.xml stuff definitely looks solid.

@ichigo if you're still interested in working on the issue we discussed this should be very helpful: ☝️

@timgilbert btw, the cljdoc link (about scm tags and stuff) links to a non-canonical version of the documentation

For now this is the canonical link: https://github.com/cljdoc/cljdoc/blob/master/doc/userguide/faq.md#how-do-i-set-scm-info-for-my-project

no worries. It returns nil. Should I set this env CLJDOC_PROFILE and try?

you can try that but it's a bug that this doesn't work anymore

I assumed that the custom aero/slurp reader would only be called if the profile is prod but now that I think about it that was probably a stupid assumption 😄

Oh, I'll update the README, thanks

np, thanks for the toolz 🙂

Sure, let me know if there's anything I can improve. I guess one thing is I'm not sure if it's possible to skip the version-rewriting if you want to just rewrite the other tags, that won't be too hard to add

try just touch resources/CLJDOC_VERSION if you want to get unblocked

I'll get this fixed later today

Yes, this works for now. Thanks :simple_smile: Do you want me to add an issue?

I think I'll just fix it now and we can save the time writing an issue 🙂

but thanks for offering it 🙂

I think something is up with CI as well. Errs at this step:

#!/bin/bash -eo pipefail
docker login -u $DOCKER_USER -p $DOCKER_PASS
Password: EOF
Exited with code 1

should be fixed in master now

you might need to rebase to get the change into your branch

👍