Step 'eclipse groovy formatter' found problem in 'src\test\groovy\io\opentelemetry\smoketest\AppServerTest.groovy':
Multiple problems detected during step execution:
Snippet4e0e929340b5448790023a3e8b406651.groovy: 57: unexpected token: abstract @ line 57, column 15.
         !helper.abstract
                 ^
Snippet4e0e929340b5448790023a3e8b406651.groovy: 57: expecting '}', found 'abstract' @ line 57, column 15.
         !helper.abstract
                 ^
Snippet4e0e929340b5448790023a3e8b406651.groovy: 57: expecting '}', found 'abstract' @ line 57, column 15.
         !helper.abstract

anyone knows Snippet4e0e929340b5448790023a3e8b406651.groovy?

The error reporting is a bit confusing. Anyway this should be

The error reporting is a bit confusing. Anyway this should be

opentelemetry-java-instrumentation/muzzle/src/test/groovy/io/opentelemetry/javaagent/tooling/muzzle/HelperReferenceWrapperTest.groovy

Line 54 in 67ba0a3

!helper.abstract

I guess abstract is treated as a reserved word? Seems to go away when all occurrences of abstract in this file are replaced with isAbstract(). Unfortunately this isn't the only issue, there is also .flatMap(log -> log.getResourceLogsList().stream()) that seems to go away when replaced with .flatMap { log -> log.getResourceLogsList().stream() }. Next there is java.lang.NullPointerException: Cannot invoke "org.codehaus.groovy.ast.ASTNode.getEnd()" because "nestedNode" is null that will take more effort to figure out what exactly causes it (I'd try commenting out parts of the offending file to isolate the problematic construct).
If you are going to proceed with this please see if you can change the formatting settings to 2 space indent, hopefully that way less code will need to be completely reformatted.

Thank you for looking into it. yes, there are more issues than what I expected. i will try to help convert as many groovy classes as possible to java so that we don't need to deal with groovy anymore :)

I'm going to close this PR.