@juhoteperi @donaldball @martinklepsch Thanks for the suggestions. Managed to use :exclusions. Also (uber :exclude [#"bouncycastle"]) seems to work

using :scope test also helps to exclude the libs from the final jar

but I have to also exclude the transitive dependencies of buddy-core in order for that to work

Can I use boot to build a java project?

and if yes, how?

well there is a javac boot task, I guess it depends on how complicated your java sources are

@chris oh I hadn’t realised; perfect, thanks!

that was easy

@juhoteperi that scopes it for the pom.xml, but the aot code in clojure isn't aware of scopes.

aot actually brings in test scoped dependencies if you require them.

@dominicm Yeah, well, that's why I only aot compile single main namespace, nothing else

@juhoteperi there was an idea to just have the aot class have an option for bringin gin a plain ol' java shim.

so my "single main namespace" seems to require (transitively) most of my other namespaces. Is it possible to make it only compile one or two namespaces, and leave the rest as clojure. I'm getting issues with import errors because of multiple versions of library existing on the classpath due to aot.

Quite common solution is to require nothing from main ns directly, and instead use require and resolve on runtime: https://github.com/boot-clj/boot/wiki/Circumnavigating-Watch-and-AOT-Compilation-Limitations

So how can I cause boot to pass arguments passed to a task onto the program like is done if I do something like lein run -p 3000. How do I define the arguments to (deftask run) in boot? Basically the equivalent of [& args] for tasks

@donyorm this might be helpful: https://github.com/boot-clj/boot/wiki/Task-Options-DSL#positional-parameters

that could work. Not as clean, but possible

@donyorm had the same question, had to settle for positional arguments

well it'll work, and it makes sense within the contex of boot. I've been updated the luminus documentation to include boot commands, and I realized that the boot version of luminus didn't actually support setting the port by commandline arguments