Surefire plugin "systemPropertyVariables" are not propagated by default in "package" or "application wide" JUnit Eclipse "Run configurations"

[l0new4nder3r]

Hi all,

After encountering the dreaded "eclipse does not propagate systemPropertyVariables settings from surefire in JUnit tests by default" behaviour once more today (no, my quarkus test profile tests were just fine), I wanted to know what the status was (using latest version release of Eclipse, currently 2025-12) on this.

I checked a few SO posts and issues here and there, and was delighted to see that @treilhes (thanks a lot! <3) did an amazing job (that I completely missed) to tackle this, last year.

But it took me a while to realise that it was working fine, though only on single test classes, and this puzzles me.
I usually run the JUnit classes by package, or for a whole app.
And it seems that, in these cases, the feature does not work - even after deleting and recreating a new "run configuration".

Am I doing something wrong here?
Or is it really the case, and if so: is there a good reason for this limitation?

[kwin]

The culprit is in

m2e-core/org.eclipse.m2e.jdt/src/org/eclipse/m2e/jdt/internal/UnitTestSupport.java

Line 326 in d06b1b2

.filter(e -> isTestHandledByPlugin(facade, monitor, e, testClass)).toList();

. It first extracts the relevant class from the launch configs attribute org.eclipse.jdt.launching.MAIN_TYPE (which is empty for package runs) and then tries to find to MojoExecution covering that empty class.

For package/project runs the attribute org.eclipse.debug.core.MAPPED_RESOURCE_PATHS is used to specify the executed package or project.