Tibor Digana commented on SUREFIRE-1476:


I have notice the same issue 2 weeks ago.

It looks to me that current version is using environment variable CLASSPATH or 
the CLI param {{-cp}} instead.

One thing to confirm different implementation would be to open the sources of 
version {{2.12.4}} where the behavior was as expected last time.

It looks to me that this old version used {{IsolatedClassLoader}} class if 
\{{useSystemClassLoader=false}}, but this is only my guess.

We have one page regarding class loading and this should be checked as well.

> 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

Reply via email to