Bug in Surefire 3.0.0-M4

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug in Surefire 3.0.0-M4

Francois MAROT
Hello all,
just want to notify of a bug we found today when switching our surefire
version from 2.x.y to the latest 3.0.0-M4 (
https://blogs.apache.org/maven/entry/apache-maven-surefire-version-3 ). It
creates problems with environment variables which seem to be incorrectly
set. As a consequence, my PATH is not set correctly and my DLL which needs
to load another DLL (and uses the PATH for this) cannot.
We switched back to 3.0.0-M3 where the bug was not present.
For now I haven't created a Short, Self Contained, Correct example, but I
could create it to help track the bug if needed. I just wanted to make sure
this was not a known issue and already reported.

Regards
Fran├žois



--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Bug in Surefire 3.0.0-M4

Francois MAROT
Here is a self contained test in a single pom with no other files that
demonstrates the problem:
https://gist.github.com/fmarot/3bc638212e52ff1e0c55843c7fb6bbaa

The problem being that pre-existing env variable are not redefined even if
explicitly set in surefire.



--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]