#error {
 :cause "Could not locate de/yobst/yobst_core/test_utils__init.class, de/yobst/yobst_core/test_utils.clj or de/yobst/yobst_core/test_utils.cljc on classpath. Please check that namespaces with dashes use underscores in the Clojure file name."
 :via
 [{:type java.io.FileNotFoundException
   :message "Could not locate de/yobst/yobst_core/test_utils__init.class, de/yobst/yobst_core/test_utils.clj or de/yobst/yobst_core/test_utils.cljc on classpath. Please check that namespaces with dashes use underscores in the Clojure file name."
   :at [clojure.lang.RT load "RT.java" 462]}]

another odd behaviour is that I can load the test-utils-ns once in the repl but the second time it tells me Namespace not found ...

What IDE are you using?

no IDE, vim 🙂

with conjure

tests are running fine, it's only in the repl

I'm going on a trip today and will be quite busy this coming week, so hopefully someone in the community can help you with this, or @U2BDZ9JG3 if he has time.

ok, no problem. thanks anyway

Good luck!

Which poly command is giving this error?

it's not the poly tool that gives the error. when I started a repl I get an error on loading my namespaces

it does not find the test-util namespace and I don't know how to get rid of this problem. as written above poly ws out shows the namespace is there and clj -A:test:dev -Spath also shows the classpath with the test-directory

Maybe you can createa small repo where you reproduce the problem and share it here?

yeah, right. maybe I just try that

or renaming the file probably

projects/<name>/resources/logback.xml -- matches what we do with log4j2.properties for all our projects. And the dev/repl one goes in development/resources/ and make sure that in on your :dev > :extra-paths

where would you put the test-resources? the logback or log4j2.properties for testing?

i assume they are going into the project right? with a test-alias and a test-resources directory, right?

We use a JVM property during testing to specify a test-only log4j2.properties file, as I recall. But you could try something with a :test alias in projects/<name>/deps.edn for that -- I think you'd end up with both the production version and the test version on your path unless you use a test-specific name for the file?

-Dlog4j2.configurationFile=/var/www/worldsingles/development/resources/log4j2-silent.properties -- since we know every env will always have that path (dev/test/CI/QA/production)

@U04V70XH6 and how do you use conditional rendering in .properties? Because you can use arbiters in xml, but this is not supported in .properties, so I'm wondering what's a good way to run something based on env there?

We haven't found the need for that. An env var can specify which .properties file to use (and can be overridden by JVM opts) and that's been enough for us.

And are you building whole .properties file from scratch, or are you using multiple files during run (e.g. with configurationFile)?

I'm not sure what you're asking... we have three static properties files: one for dev, one for test, one for deployment.

We originally wrote them "from scratch" I guess but they rarely change now. Occasionally we need to add a new library's config to set a default level.