holy-lambda 2022-12-08 | Slack Archive

Jamie Walkerdine09:12:38

Hi folks - so it seems like there's some kind of cacheing going on with HL - we have a project with four directories (for four lambdas) and each one is the root of its own HL project (Babashka runtime). We've noticed that if two projects have files with the same namespace (that do separate things) often the synchronization of dependencies will get muddled up (It will take the files for the source from the wrong place) even when being called from the right project. E.G., you can see in the screenshots that the ConfigLambda points to its own src, and has certain files there, but the source files are being pulled from a different place. Is there any way to fix this issue? Update it actually doesn't seem to depend on namespaces.

Jamie Walkerdine11:12:50

I get these warnings when I sync - maybe related?

[holy-lambda] Command <hl:babashka:sync>
{:warning "clashing jar item", :path "native-agents-payloads/1.edn", :strategy :noop}
{:warning "could not find classpath entry", :path "/home/jam/.gitlibs/libs/org.babashka/spec.alpha/1a841c4cc1d4f6dab7505a98ed2d532dd9d56b78/src/main/java"}
{:warning "could not find classpath entry", :path "/home/jam/.gitlibs/libs/org.babashka/spec.alpha/1a841c4cc1d4f6dab7505a98ed2d532dd9d56b78/src/main/resources"}
{:warning "clashing jar item", :path "META-INF/services/com.fasterxml.jackson.core.JsonFactory", :strategy :concat-lines}
{:warning "clashing jar item", :path "META-INF/services/com.fasterxml.jackson.core.JsonFactory", :strategy :concat-lines}
{:warning "clashing jar item", :path "META-INF/versions/11/module-info.class", :strategy :noop}
{:warning "clashing jar item", :path "META-INF/versions/11/module-info.class", :strategy :noop}

Jamie Walkerdine13:12:46

Update: Running bb -Sforce before sync'ing the dependencies fixed the issue

2022-12-08

Channels