The solution is to understand the root cause after the analysis has been done. We should start with observing classpath. Why it is different with reused forks.
On Thu, Sep 6, 2018 at 11:39 PM Christian Stein <[email protected]> wrote: > @mureinik <https://github.com/mureinik> reported a side-effect with > reuseForks=false over at junit-team/junit5#1579 > <https://github.com/junit-team/junit5/issues/1579> -- does this PR also > fixes this issue? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/maven-surefire/pull/193#issuecomment-419250240>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AA_yRzxUHuC7bL7lbQfcuRXA9QgYCzB6ks5uYZYogaJpZM4WZuXq> > . > [ Full content available at: https://github.com/apache/maven-surefire/pull/193 ] This message was relayed via gitbox.apache.org for [email protected]
