Closed jetztgradnet closed 13 years ago
Great!
However, this makes the standard Erjang (e.g. running ./ej) very verbose; perhaps you can provide a default logger that does something reasonable like just ignoring INFO logging messages?
Probably it is enough to change most log.info() calls to log.fine(), as running on INFO should only show interesting stuff, but not flood the log/console. I will have a look tonight.
Kresten, would you please try again? Now there shouldn't be any logging messages, when simply starting erjang using ej
Replaced a zillion System.err.println() calls with proper logging using java.util.logging.Logger. The logging configuration must be provided by the user or reside on the classpath.
The next step (in another branch) will be to make the IO streams configurable at one place and to properly shutdown Erjang without calling System.exit().