apache / apache/maven-surefire

[SUREFIRE-1592] Forked JVM should load classes in Isolated ClassLoader if useSystemClassLoader=false

Open
#2,212 0 comments 0 reactions 0 assignees View on GitHub
enhancement priority:major
Dominant language
Java
Stars
461
Forks
588
Avg merge
1d 8h
Merged PRs (30d)
19

Description

**[Tibor Digana](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tibor17)** opened **[SUREFIRE-1592](https://issues.apache.org/jira/browse/SUREFIRE-1592?redirect=false)** and commented

The Surefire project runs itself tests within `maven-surefire-plugin:2.12.4` which properly isolates project classes and plugin's classes. The current versions 2.x do not have this ability. The version `3.0.0` should load user's classes in `IsolatedClassLoader` (configured by `useSystemClassLoader=false`).

---
No further details from [SUREFIRE-1592](https://issues.apache.org/jira/browse/SUREFIRE-1592?redirect=false)

Contributor guide

Open the contributing guide

Research direction

No source files or tests are identified in the issue. Start by tracing how the forked JVM handles useSystemClassLoader=false and how user classes are currently loaded. Done means version 3.0.0 loads those user classes through IsolatedClassLoader while preserving plugin class isolation.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.