Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for muting the feature set being sent to standard output on init #8

Open
ekmett opened this issue Oct 20, 2019 · 3 comments
Open

Comments

@ekmett
Copy link

ekmett commented Oct 20, 2019

I love jabel so far, and have been gleefully sprinkling var throughout my code. It does, however, rather severely increase the verbosity of large multi-project builds. It would be nice if we could ask via a flag or other mechanism to disable to infodump during init. It would let me see my errors again. ;)

There are a few options, the most gradley(?) way would probably be to use the log level to choose whether or not to report it.

@bsideup
Copy link
Owner

bsideup commented Oct 21, 2019

Hi @ekmett,

I must admit my decision to use STDOUT is... questionable indeed :D
I will make it use the standard logger of the compiler, so that it will follow the rules applied to javac itself.

Thanks for reminding me about it! 👍

@astubbs
Copy link

astubbs commented Aug 12, 2020

Took a crack at it, but can't seem to hook into the proper logging system still...

@lessthanoptimal
Copy link

How about replacing System.out with a reference to a class field PrintStream out that by default points to System.out. In the gradle plugin you could have a verbosity flag. If set to false pipe it into a null stream https://stackoverflow.com/questions/691813/is-there-a-null-outputstream-in-java

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants