Thx Romain. My gmail really did not show me the begin of this thread. Now in the mail-archive.apache.org i see that it was related to Dejan's work. The work is still in progress and we have some issues with CNFE which is still okay.
For all, currently "surefire-junit4" is activated by default if e.g.junit:junit:4.12 appears in test dependencies. Here in Dejan's change, we attempt to make "surefire-junit47" activated as default Provider for libraries JUnit 4.7+. It is a little upgrade regarding JUnit4.x after years. We know that the feature "re-run" works other way in both providers and this has to be well documented for the users. It would not affect other providers, namely JUnit5, JUnit3 and TestNG. On Fri, Aug 23, 2019 at 6:47 AM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Hi Martin, > > Here it is fully unrelated but more a setup issue, see previous Tibor's > answer. > > @Tibor: topic was changed do your mailbox didnt see the trick but thread is > available at > https://mail-archives.apache.org/mod_mbox/maven-dev/201908.mbox/browser > > > Le ven. 23 août 2019 à 00:45, Tibor Digana <tibordig...@apache.org> a > écrit : > > > I don't know what Jira issue you are refferring to. > > The ICL is used due to user's filtering and the multiple fork VMs. > > > > On Fri, Aug 23, 2019 at 12:40 AM Martin Gainty <mgai...@hotmail.com> > > wrote: > > > > > CNFE when running surefire means > > > Isolated (TEST) Classloader cannot load the dependency containing that > > > class > > > In your case that dependency is junit > > > > > > if it was up to me i would discontinue use of Isolated Classloader in > > > favour of using system classloader > > > the only reason Isolated cl was used was the path limitation for System > > > ClassLoader (initially 4k) > > > now all paths including CLASSPATH can be 32k so restricted classpath > > > length should not be an issue > > > > > > ymmv > > > martin- > > > > > > > > > > > >
