Hubert Plociniczak 352ad06d2f Reduce extra output in compilation and tests (#7809) ... * Reduce extra output in compilation and tests I couldn't stand the amount of extra output that we got when compiling a clean project and when executing regular tests. We should strive to keep output clean and not print anything additional to stdout/stderr. * Getting rid of explicit setup by service loading In order for SL4J to use service loading correctly had to upgrade to latest slf4j. Unfortunately `TestLogProvider` which essentially delegates to `logback` provider will lead to spurious ambiguous warnings on multiple providers. In order to dictate which one to use and therefore eliminate the warnings we can use the `slf4j.provider` env var, which is only available in slf4j 2.x. Now, there is no need to explicitly call `LoggerSetup.get().setup()` as that is being called during service setup. * legal review * linter * Ensure ConsoleHandler uses the default level ConsoleHandler's constructor uses `Level.INFO` which is unnecessary for tests. * report warnings		2023-10-16 10:57:44 +02:00
..
java/org/enso/interpreter/test	Towards shallow nesting in IR (#7681)	2023-08-31 15:42:53 +00:00
resources	Reduce extra output in compilation and tests (#7809)	2023-10-16 10:57:44 +02:00
scala/org/enso/interpreter/test/instrument	Reduce extra output in compilation and tests (#7809)	2023-10-16 10:57:44 +02:00