4 ms·
> a multi-dependency project in the getting started page That's because they basically don't support monorepo multi-module projects. It's incredibly tedious an
by __jem 4y ago
> a multi-dependency project in the getting started page
That's because they basically don't support monorepo multi-module projects. It's incredibly tedious and makes me long for something like Maven or Gradle (tools that otherwise are often too complicated).
- lvh 4y agoHow do you mean? You can specify local (fs) dependencies fine, which is presumably what you want in that scenario? (I regularly contribute to a monorepo like this, though admittedly the top-level components are relatively disjoint.)
- __jem 4y agoI mean, you can hack something together with local dependencies, yes, but there's no out of the box way to build and test everything together, or to do things like pin dependency versions across projects, have projects inherit shared configuration, etc. We end up creating a bunch of pseudo-projects that contain things like single dependencies, but this blurs the line between build time concerns and actual source code. As with everything in clojure, you can write it all yourself using something like tools.build, but it's not convenient and clearly not a first class use case.
- weikju 4y agoI wonder if Polylith would be up your alley? https://polylith.gitbook.io/polylith/ https://polylith.gitbook.io/polylith/