@hlship yeah this is something I was going to post on your ML thread

I've been thinking it would be really handy to have a way to detect class conflicts

atm, you can only detect and visualise conflicts at the JAR level based on artifactID. However sometimes two different artifact's share the same class packages

This is especially devious when you're trying to resolve leiningen classpath issues, because lein deps 🌲 is never going to show you conflicts with classes in the lein uberjar

I’ll probably end up forking org.flatland/protobuf so update it to latest Google protobuf and not repackage those classes!

Project hasn’t been updated in years.

hi folks! is it possible to generate several artifacts with leiningen? Say, I want to generate uberjar for the service and jar for client library for this service (generated based on spec/schema API). any pointers on how I can achieve this?

@larhat make an alias with a "do" and run several commands together

:aliases          {
                     "build-jars" ["with-profile" "+dev-run" "do"
                            ["clean"]
                            ["jar"]
                            ["uberjar"]]
...

danielcompton thanks, I will look into this. The idea is to have uberjar with all the code for the service, and small jar, generated from schema with the client api. maybe do will help