Cloning the
grails-release plugin, cding to the directory and grails test-app in Grails 2.0.4 gives
| Error Compilation error compiling [unit] tests: startup failed:
C:\Users\Master\Documents\Programming\grails-release\test\unit\grails\plugins\publish\maven\MavenDeployerUnitTests.groovy: -1: A transform used a generics containing ClassNode groovy.lang.Closure <V extends java.lang.Object -> java.lang.Object> for the method protected java.lang.Object play(groovy.lang.Closure closure) { ... } directly. You are not suppposed to do this. Please create a new ClassNode refering to the old ClassNode and use the new ClassNode instead of the old one. Otherwise the compiler will create wrong descriptors and a potential NullPointerException in TypeResolver in the OpenJDK. If this is not your own doing, please report this bug to the writer of the transform.
@ line -1, column -1.
C:\Users\Master\Documents\Programming\grails-release\test\unit\grails\plugins\publish\maven\MavenDeployerUnitTests.groovy: -1: A transform used a generics containing ClassNode groovy.lang.Closure <V extends java.lang.Object -> java.lang.Object> for the method protected java.lang.Object with(java.lang.Object mock, groovy.lang.Closure closure) { ... } directly. You are not suppposed to do this. Please create a new ClassNode refering to the old ClassNode and use the new ClassNode instead of the old one. Otherwise the compiler will create wrong descriptors and a potential NullPointerException in TypeResolver in the OpenJDK. If this is not your own doing, please report this bug to the writer of the transform.
@ line -1, column -1.
Is there supposed to be a different procedure for running these? Expected behavior?
Not sure if that's JIRA bug worthy, but might be good fix. :)
--
Nick Vaidyanathan
Locked
