Re: Surefire CNFE

2019-08-23 Thread Tibor Digana
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

Re: Surefire CNFE

2019-08-22 Thread Romain Manni-Bucau
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

Re: Surefire CNFE

2019-08-22 Thread Tibor Digana
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 wrote: > CNFE when running surefire means > Isolated (TEST) Classloader cannot load the dependency containing that > class > In

Re: Surefire CNFE

2019-08-22 Thread Martin Gainty
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