See here: blog.sebastian-daschner.com/entries/linux-terminal-font-alacritty-jetbrains-mono-emoji I'm using the same font in my IDE (that was the default)

Nowadays, all of my enterprise client projects are built with Maven. I like that the projects are very predictable (often the inflexibility of Maven is said to be a feature), people know what to expect, and for at least 99% of projects, the Maven/Java/project structure is sufficient

@@SebastianDaschnerIT Thank you Sebastian, I did think it was interesting Quarkus is also using Maven so i'm not sure what the benefit would be from Gradle usage.

No, exactly not. That's the issue I see, it's confusing :) `mvn verify` can be thought of as an alias of `mvn package`. The `verify` aspect defines more phases, e.g. one that is called `integration-test`, which (confusingly) is not the same as failsafe:integration-test. To make `verify` actually run our *IT.java classes, you'd need to make extra configuration. Have a look at this list here: maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#lifecycle-reference (`integration-test` is listed there, however our *ITs won't be run). In a nutshell that's why: too confusing, `package` is much clearer from the name :)