[
https://issues.apache.org/jira/browse/SUREFIRE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369413#comment-16369413
]
Ivan Kelly commented on SUREFIRE-1476:
--------------------------------------
2.8.1 is the last version that worked correctly for me. With 2.9 and above the
test case linked fails.
> useSystemClassLoader=false doesn't work as expected after 2.8.1
> ---------------------------------------------------------------
>
> Key: SUREFIRE-1476
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1476
> Project: Maven Surefire
> Issue Type: Bug
> Reporter: Ivan Kelly
> Priority: Major
>
> I have a test case where I want to load a bunch of jars in a custom
> classloader, and check that they are isolated from the classes in the
> classloader within which the test is running. This is for BC testing
> elsewhere in my code.
>
> See
> [https://github.com/ivankelly/bookkeeper/blob/faa9f6db6f6861b9579be441227621bb06f0fac8/tests/integration-tests-utils/pom.xml]
>
> Run test in that module to see it work correctly. Change the surefire plugin
> to a newer version to see it fail. The problem seems to be that all
> dependencies are being added to the classpath of the forked processes, so no
> matter what happens, they are in the system class loader.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
