keeganwitt / gmock

Automatically exported from code.google.com/p/gmock
6 stars 2 forks source link

GMock 0.8.1 doesn't work with groovy 1.8.3+ #119

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
GMock test cases using the @WithGMock annotation fail to compile with groovy 
1.8.3 or higher with the following error:

/mypath/something.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 unordered(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.

A similar bug was reported and fixed in 115. I've confirmed that a build from 
the latest source does not have this problem.

Is there a timeline for a new release (post 0.8.1) to release this fix?

(We would also like the fix for 116 if possible in a labelled release as my 
team is uncomfortable depending on trunk. Is there anything to prevent you 
cutting a new release soon?)

Thanks,
Sean

Original issue reported on code.google.com by jkarthau...@equalexperts.com on 29 Nov 2011 at 10:47

GoogleCodeExporter commented 9 years ago
(and Joe!)

Original comment by jkarthau...@equalexperts.com on 29 Nov 2011 at 10:48

GoogleCodeExporter commented 9 years ago
I tried both groovy 1.8.3 and 1.8.4, and it doesn't report those errors any 
more.

Are you use grails 2.0 RC1? But our tests already cover that. Please submit a 
reproducible test.

PS: I will talk to julien about the release timeline.

Original comment by JohnnyJianHY on 29 Nov 2011 at 11:42

GoogleCodeExporter commented 9 years ago
Hi there,

Yes we can confirm that the issue *is fixed* in the latest build (from source). 
We agree that no further source code patches are necessary. All we're asking 
about is the release timeline to get this fixes officially.

P.S. we don't use grails at all. We got the error in a groovy jersey app.

Original comment by jkarthau...@equalexperts.com on 29 Nov 2011 at 11:59

GoogleCodeExporter commented 9 years ago
OK. As this is a high priority bug, I think we will release soon.

Original comment by JohnnyJianHY on 29 Nov 2011 at 12:03