Martin Klepsch

Thinking more about this the core really is that there are multiple pom files in the fileset once you use `uber` maybe instead of introducing yet another option we could...

So a solution that does not require any code changes is passing a proper `:exclude` set to the `uber` task this: ``` (uber :exclude #{ #"(?i)^META-INF/INDEX.LIST$" #"(?i)^META-INF/[^/]*\.(MF|SF|RSA|DSA)$" #"META-INF/maven/" }) ```

Maybe it should be the default? I don't see why (by default) you'd want multiple `pom.xml` inside your uberjar.

Hey, can you check the value of ``` (deref boot.util/*colorize?*) ``` Ideally check for the value when you start Boot using `boot -C repl` and `boot -C repl -C`.

@mbuczko the system that detects filesystem changes may trigger multiple. For that there's a debounce of 10ms. If you increase the debounce that should reduce the number of triggered runs....

As pointed out in Slack the culprit seems to be the `(remove A-Z? ...)` line in [boot.cli](https://github.com/boot-clj/boot/blob/ac835cea8c18e926bb843e01579b86e3f30458d2/boot/core/src/boot/cli.clj#L48). Not sure what the `loop` in that function does I just did some...

A similar situation arises when using the `uber` task. Currently dependencies are taken from the global env but there might be utility in reading them from a generated `pom.xml`. Related...

@mprokopov Would you be interested in providing a PR for this? 🙂

I think `org.clojure/clojure` is a special case here because you need to specify it in two places: `build.boot` and `boot.properties`. This does not apply to libraries where this warning usually...

@mprokopov hey again! Just wanted to check what you think about my suggestion and if you’d be interested to help with this? 🙂