PowerMock doesn't work correctly when using cobertura and Maven about powermock HOT 10 CLOSED

There seems to be a work-around: 
  <build>
  <plugins>
     <plugin>
        <artifactId>maven-surefire-plugin</artifactId>
        <configuration>
            <forkMode>pertest</forkMode> 
        </configuration>
      </plugin>
     </plugins>
  </build>

The workaround is good enough for now

I don't think workaround is good enough. With the work around, I still get the
Unable to get lock on
/home/h_maf/hudson/data/jobs/mplus-services-applications/workspace/mplus_service
s/applications/routing/ServiceEndpointRouter/target/cobertura/cobertura.ser.lock
:
null
This is known to happen on Linux kernel 2.6.20.
Make sure cobertura.jar is in the root classpath of the jvm 
process running the instrumented code.  If the instrumented code 
is running in a web server, this means cobertura.jar should be in 
the web server's lib directory.
Don't put multiple copies of cobertura.jar in different WEB-INF/lib directories.
Only one classloader should load cobertura.  It should be the root classloader.

The workaround is not good enough since it slows our build down from 40s to 14
minutes!! Can someone unfix this issue and suggest a more appropriate solution?

I looked into it a year ago and I couldn't find any solution other than this. 
It's
quite a known problem if you google for it. If you have any ideas on how to 
solve
this please share them with us.

[deleted comment]

Ignore my last comment. New issue is here:
http://code.google.com/p/powermock/issues/detail?id=122

Take a look at issue 122 here as there is a simple fix for this:
http://code.google.com/p/powermock/issues/detail?id=122#c5

This is excellent news. Thank you so much!