Dominik Gedon

Nice improvement. I did implement this myself yesterday.

Can you please check whether a CLA was already signed by @SUSE?

That is indeed weird. My collegues an I tested it on 4 different machines and we all got the same error.

> What maven version are you using? ```shell $ mvn --version Apache Maven 3.6.3 (SUSE 3.6.3-lp152.2.31) Maven home: /usr/share/maven Java version: 11.0.7, vendor: Oracle Corporation, runtime: /usr/lib64/jvm/java-11-openjdk-11 Default locale: en_US,...

~~I am still waiting for a response of our legal team.~~ Our legal team will sign the CLA and I myself have signed the individual CLA, too.

Without rebasing this works now: ```shell $ mvn dependency\:analyze [INFO] Scanning for projects... [INFO] [INFO] --------------------------< org.jitsi:jibri >--------------------------- [INFO] Building jibri 8.0-SNAPSHOT [INFO] --------------------------------[ jar ]--------------------------------- [INFO] [INFO] >>> maven-dependency-plugin:2.8:analyze...

```shell $ mvn clean test [INFO] Scanning for projects... (...) [INFO] ------------------------------------------------------- [INFO] T E S T S [INFO] ------------------------------------------------------- ~~~ Kotest Configuration ~~~ -> Parallelization factor: 1 -> Concurrent...

``` $ java --version openjdk 11.0.10 2021-01-19 OpenJDK Runtime Environment (build 11.0.10+9-suse-2.1-x8664) OpenJDK 64-Bit Server VM (build 11.0.10+9-suse-2.1-x8664, mixed mode) ```

I am on 204354dc060cea694cde6ffe9903f3c180487a56 right now and `mvn dependency:analyze` works, too but `mvn clean test` still fails as shown above.

You mean that we have colored output?