Groovy++ shouldn't modify the AST of things that aren't annotated with @Typed

[GoogleCodeExporter]

I was trying out Groovy++ and simply including the .jar on my classpath caused 
some of my unit tests to start failing.  I didn't add @Typed to anything in my 
code yet, but Groovy++ must have made some AST modifications anyways.

Removing the groovy++ jar made the unit tests succeed again.

Groovy++ should only make any modifications to things that say @Typed. 

This is with groovy++ 0.4.150 and groovy 1.7.5.

Original issue reported on code.google.com by kwste...@gmail.com on 26 Jan 2011 at 5:51

• Merged into: #301

[GoogleCodeExporter]

It will help a lot if you could mention what piece of code started to fails. 
Thanks a lot.

Original comment by alex.tka...@gmail.com on 26 Jan 2011 at 5:54

[GoogleCodeExporter]

My code does an AST transformation itself. It performs some checks on methods 
and class level closures to report possible programming errors.  After 
including groovy++, it seems that none of the checks were being done on class 
level closures anymore.

Checks on things like "def method(){...}" still work fine. Checks on things 
like "def method = {...}" no longer worked.

Original comment by kwste...@gmail.com on 26 Jan 2011 at 7:51

[GoogleCodeExporter]

I am not sure I understand exactly what's going on here. Need more information 
like compilation phase you use, what ast elements you are looking for and 
missing etc.

Original comment by alex.tka...@gmail.com on 27 Jan 2011 at 11:20

[GoogleCodeExporter]

Original comment by alex.tka...@gmail.com on 6 Feb 2011 at 5:39

• Changed state: Duplicate