通过surefire-plugin更改要加载的类路径上的位置顺序

Question

Does anybody know how to change it ?

I mean from

target/test-classes ... target/classes .... maven dependencies

to

target/test-classes ... maven dependencies .... target/classes 

It relates to this surefire-plugin feature request

It's because surefire-plugin cannot include/exclude resources from /target/classes ... it can only include/exlude resources via <testResources> element which can affect only /target/test-classes, not /target/classes

It all happens here in Surefire-plugin :

File projectClassesDirectory = new File( project.getBuild().getOutputDirectory() );
if ( !projectClassesDirectory.equals( classesDirectory ) )
{
    int indexToReplace = classpathElements.indexOf( project.getBuild().getOutputDirectory() );
    if ( indexToReplace != -1 )
    {
        classpathElements.remove( indexToReplace );
        classpathElements.add( indexToReplace, classesDirectory.getAbsolutePath() );
    }
    else
    {
        classpathElements.add( 1, classesDirectory.getAbsolutePath() );
    }
}

File projectTestClassesDirectory = new File( project.getBuild().getTestOutputDirectory() );
if ( !projectTestClassesDirectory.equals( testClassesDirectory ) )
{
    int indexToReplace = classpathElements.indexOf( project.getBuild().getTestOutputDirectory() );
    if ( indexToReplace != -1 )
    {
        classpathElements.remove( indexToReplace );
        classpathElements.add( indexToReplace, testClassesDirectory.getAbsolutePath() );
    }
    else
    {
        classpathElements.add( 0, testClassesDirectory.getAbsolutePath() );
    }
}

getLog().debug( "Test Classpath :" );

for ( Iterator i = classpathElements.iterator(); i.hasNext(); )
{
    String classpathElement = (String) i.next();

    getLog().debug( "  " + classpathElement );

    surefireBooter.addClassPathUrl( classpathElement );
}

Answer 1

Consider testing in a separate project. In general, when you have a project that conflicts with The Maven Way, that's the solution - split it up.

Answer 2

What I understood from your feature request link, is that you have some src/main/resources/config.xml and a dependency that also contains a config.xml that you want to use in your tests. Is that right?

If that is the case, what you could do is to move your src/main/resources/config.xml to another place (not a resource dir), like src/config/config.xml and them include it in your final JAR/WAR by setting the war or jar plugin config.

In that way your tests will see the config.xml from your dependency but not your src/config/config.xml since it is not in the classpath.