Replaced a zillion System.err.println() calls with proper logging using j #52

Merged
merged 2 commits into from Jun 17, 2011

Conversation

Projects
None yet
2 participants
Contributor

jetztgradnet commented Jun 16, 2011

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().

@jetztgradnet jetztgradnet Replaced a zillion System.err.println() calls with proper logging usi…
…ng java.util.logging.Logger. The logging configuration must be provided by the user or reside on the classpath.
2947714
Owner

krestenkrab commented Jun 16, 2011

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?

Contributor

jetztgradnet commented Jun 16, 2011

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.

Contributor

jetztgradnet commented Jun 16, 2011

Kresten, would you please try again? Now there shouldn't be any logging messages, when simply starting erjang using ej

@krestenkrab krestenkrab merged commit e990a14 into trifork:master Jun 17, 2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment