You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: