Mocks should ignore finalize() (maybe?)

When running on device (or emulator) all mocks thrown an exception when the JVM 
calls the finalize() method:

06-03 11:27:08.795: INFO/dalvikvm(4963): Ljava/lang/AssertionError;: 
06-03 11:27:08.795: INFO/dalvikvm(4963):   Un-thread-safe mock called from 
multiple threads
06-03 11:27:08.795: INFO/dalvikvm(4963):     at 
org.easymock.internal.MockInvocationHandler.invoke(MockInvocationHandler.java:32
)
06-03 11:27:08.795: INFO/dalvikvm(4963):     at 
org.easymock.internal.ObjectMethodsFilter.invoke(ObjectMethodsFilter.java:61)
06-03 11:27:08.795: INFO/dalvikvm(4963):     at $Proxy18.finalize(Native Method)
06-03 11:27:08.795: INFO/dalvikvm(4963):     at 
genmocks.java.util.PropertiesDelegateSubclass.finalize(PropertiesDelegateSubclas
s.java:-1)
06-03 11:27:08.795: INFO/dalvikvm(4963):     at 
dalvik.system.NativeStart.run(Native Method)

Perhaps mocks created by AndroidMock should automatically ignore the finalize() 
method invokation?

Technically an EasyMock issue:

http://sourceforge.net/tracker/index.php?func=detail&aid=2710478&group_id=82958&
atid=567837

But could be solved in AndroidMock fairly easily I would guess.

Original issue reported on code.google.com by jason.po...@gmail.com on 3 Jun 2011 at 6:36

TacapeForte / android-mock

Mocks should ignore finalize() (maybe?) #9