jabel icon indicating copy to clipboard operation
jabel copied to clipboard

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

Open ekmett opened this issue 5 years ago • 3 comments

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.

ekmett avatar Oct 20 '19 22:10 ekmett

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! 👍

bsideup avatar Oct 21 '19 18:10 bsideup

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

astubbs avatar Aug 12 '20 17:08 astubbs

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

lessthanoptimal avatar Aug 16 '20 15:08 lessthanoptimal