You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@groovy.apache.org by Alexander Veit <al...@dev.unitedplanet.de> on 2020/05/13 14:34:29 UTC
Collecting errors fails after upgrade from Groovy 2.5 to 3.0
Hi,
we have the following problem after switching from Groovy 2.5 to 3.0.
To check Groovy for syntax errors scripts are being compiled (with
CompilerConfiguration.DEFAULT) up to the Phases.PARSING phase.
After the upgrade to Groovy 3.0 the number of errors reported by the
ErrorCollector (getErrorCount()) is zero, even when the tested script
contains errors.
Any ideas what the problem might be?
--
Thanks in advance,
Alex
Re: Collecting errors fails after upgrade from Groovy 2.5 to 3.0
Posted by Alexander Veit <al...@dev.unitedplanet.de>.
> Groovy 3 does nothing at the PARSING phase, you could use CONVERSION phase
> instead.
This seems to work. Thank you very much Daniel.
Re: Collecting errors fails after upgrade from Groovy 2.5 to 3.0
Posted by "Daniel.Sun" <su...@apache.org>.
Hi Alex,
Groovy 3 does nothing at the PARSING phase, you could use CONVERSION phase
instead.
P.S. Groovy 3 parses source code into CST and constructs AST at the
CONVERSION phase.
Cheers,
Daniel Sun
-----
Apache Groovy committer & PMC member
Blog: http://blog.sunlan.me
Twitter: @daniel_sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html