mirror of
https://github.com/enso-org/enso.git
synced 2024-11-23 16:18:23 +03:00
352ad06d2f
* 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 |
||
|---|---|---|
| .. | ||
| THIRD-PARTY | ||
| .enso.portable | ||
| README.md | ||
Enso CLI
Actionables for this file:
- This is just a draft of the file that will be included inside the launcher distribution. It should be completed when the launcher is implemented.
Installation
The Enso distribution is portable, you can put this directory wherever you want
on your system. For example you can put it at ~/.enso.
It is a good idea to add the bin directory to your system PATH so that you
can run Enso just by typing enso in any directory.
Usage
Actionables for this section:
- Fill in examples showing how to use the launcher.
Distribution structure
Actionables for this section:
- This should explain the structure of enso distribution directory, based on the documentation.