Stefan Oehme created SUREFIRE-1655:
--------------------------------------
Summary: Surefire leaks classloaders when using in-process strategy
Key: SUREFIRE-1655
URL: https://issues.apache.org/jira/browse/SUREFIRE-1655
Project: Maven Surefire
Issue Type: Bug
Components: Maven Failsafe Plugin, Maven Surefire Plugin
Reporter: Stefan Oehme
The test classloader is created
[here|[https://github.com/apache/maven-surefire/blob/7149edc6f24fa8bff06372e24a177e86d4960d8c/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/InPluginVMSurefireStarter.java#L77]],
but never closed. As a result, the underlying JARs in that classloader remain
open and cannot be deleted. Also, their content can be stale when opened using
java.util.ZipFile.
This is a problem when running Maven integration tests using the
Embedded3xLauncher. We are developing a Maven extension and want to make sure
it works well with surefire/failsafe. This classloader leak means we have to
use a forking launcher instead, which slows down our tests considerably.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
