tools-deps

seancorfield 2025-09-16T21:32:45.204969Z

I was a bit surprised that mvn-pom skips all :local/root dependencies so you don't get subproject dependencies -- but list will list all of those dependencies (as well as all the :local/root directories). I don't see a documented way to force mvn-pom to not skip things. Is there an undocumented way?

Alex Miller (Clojure team) 2025-09-16T21:39:37.555709Z

And do what instead?

seancorfield 2025-09-16T21:40:44.123249Z

The context is Polylith, where all the subprojects are :local/root dependencies and the expectation is all of their transitive deps would need to go into pom.xml...

seancorfield 2025-09-16T21:42:43.738619Z

I mean, I get that :local/root deps themselves can't go in the POM, just like git deps can't. But for a library produced by Polylith -- or, in the OP's case, security scanning requires a pom.xml file -- the transitive deps would need to be declared...

Alex Miller (Clojure team) 2025-09-16T21:44:10.542179Z

I guess if that is in some way useful it could probably be done

seancorfield 2025-09-16T21:44:38.652879Z

I suggested -X:deps list to the OP as a way to at least get a full list of transitive deps that they could probably transform to a pom.xml but it would be nice if there was a way to leverage deps' POM generation more directly.