-
Notifications
You must be signed in to change notification settings - Fork 84
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
-quiet reports some internal parsing/ANTLR messaging #526
Comments
That's definitely ANTLR. I think we have to hook in the the ANTLR logging mechanism to eat that one. https://stackoverflow.com/questions/25990158/antlr-4-avoid-error-printing-to-console |
That might need to happen at the cfparser level.... |
Ok, if it's too hard and messy then let's leave the ticket open but not do anything about it for now. It'd have just been nice to be truly quiet with -q. But I'm not even sure what the demand for this -q functionality is... |
Documented that ANTLR/CFParser might push out text even if CFLint runs quietly. |
I think it's worth doing and not too hard. I may enter an echo ticket in the cfparser project if needed. |
fixed in cfparser 2.6.1 , release and should hit maven this weekend. |
Awesome @ryaneberly - so I'll just need to update the dependency in CFLint to 2.6.1 in a couple of days? |
right. keep an eye on maven. |
Moving to 1.4.1 since it looks like 1.4.0 is running on cfparser 2.6.0. |
... a leftover from #329:
I occasionally get messages like this (even in -q mode)
"line 1:3 no viable alternative at input 'GCfailed'"
Are they coming from cfparser? Or would those be generated in cflint somewhere? Maybe through ANTLR? Just trying to get an understanding where I could control their appearance. @ryaneberly
The text was updated successfully, but these errors were encountered: