Clojurians Log v2

The project actually shows up in lein monolith info but when running lein monolith each :in my-service test I get the "Could not resolve" err.

any thoughts on what could cause this @greg316? Assumptions about what it should find when running?

:thinking_face: might be good to make an issue for this on https://github.com/amperity/lein-monolith with some more of the context - let me peek at the code real quick

Okay will do

out of curiosity, do your subprojects use artifact groups?

checking

the lookup logic is basically: - does the selector explicitly match a subproject group/name? - does the ‘condensed’ version of the name explicitly match a subproject group/name? (e.g. a bare (defproject foo ... is actually foo/foo but can be represented in the short form) - if the target has no group, does it match exactly one subproject name? - if not, unresolved

step two seems like the highest probability for something odd happening

ok great questions. Let me do some homework and get back to you

so had the subproject name set as com.org.my-service changed it to <http://com.org/my-service|com.org/my-service> and now it works

Same fix for all 3 services.

Is there a short explanation of what the difference between these are?

@michaeljameserwin the short version is that the “group-id” is a shared namespace for many projects, while the “artifact-id” is the name of a specific project (or rather, the JAR and other artifacts produced for a project) - I don’t know if periods are legal name characters for artifact ids, which may have been part of the problem.

In most cases the subprojects in a monorepo should probably all share the same group-id, though that’s not something that lein-monolith currently checks or enforces.

This is very helpful. Many thanks!!