Surefire plugin cannot be debugged remotely by eclipse

My apologies, I used a different version of surefire plugin as dependency (source for debugging). So that it probably missed the breakpoints. So debugging Mojo works.

As to the other thing, I figured that I have to

useManifestOnlyJar=false

from here :

  if ( useJar )
    {
     File jarFile;
     try
    {
      jarFile = createJar( classPath );
    }
    catch ( IOException e )
    {
    throw new SurefireBooterForkException( "Error creating archive file", e );
    }

    cli.createArg().setValue( "-jar" );
    cli.createArg().setValue( jarFile.getAbsolutePath() );
 }
 else
 {
    cli.addEnvironment( "CLASSPATH", StringUtils.join( classPath.iterator(), File.pathSeparator ) );
    final String forkedBooter = ForkedBooter.class.getName();

    cli.createArg().setValue( shadefire ? new Relocator().relocate( forkedBooter ) : forkedBooter );
 }

But you know what ? The test(s) is not run at all if useManifestOnlyJar=false, wtf ?

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running cz.instance.transl.tests.workflow.RevolutionTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.263 sec

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

What am I doing wrong ? Why the test is not executed ? and it silently quits ?

Interesting, the test(s) runs only when :

<useManifestOnlyJar>false</useManifestOnlyJar>
<useSystemClassLoader>false</useSystemClassLoader>

I wrote a blog post that explains how impossible it is to use surefire plugin for these things. It is such a mess in the booting way and classloading that a common human being doesn't have a chance to test something more complex.

Exactly /why/ does the extract from ForkConfiguration explain anything ?

I have tried to reproduce /any/ of the symptoms/problems you describe here, and try as I may I can't reproduce any of the problems you have. All is not lost, though:

Make the necessary changes to demonstrate failure in an isolated example and then upload the diff as a patch.

I somehow sense that your main problem is escape from the confines of the isolated classloader, which is covered in the documentation https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-integration-tests/src/test/resources/additional-classpath/

Unless you can produce a working isolated failing example, this issue will be closed as cannot reproduce. If the problem would have been solved by improving the documentation, do let us know what you think should be added.

It explains that you cannot useManifestOnlyJar if you need to append stuff with wildcards to your overall classpath, see how Class-Path attribute is made in createJar method.

And if you use Isolated classloader and the code you put on classpath via additionalClasspathElements calls

currentThread.getContextClassLoader()

the classloader returned doesn't contained those classes from additionalClasspathElements...

Moreover TestNG and Junit behave differently

There was a real regression in 2.9/2.10 with forkMode=never. Use 2.8.1 until 2.11 is released. Thanks for the report