Dependency resolving with both scopes "compile" and "test"

[romain-wilbert]

Hello,

I have a maven project which has the same dependency included twice : one with a "compile" scope, another with the "test" scope and a "test-jar" type.

In the "Dependencies" tab of the launcher, i can see both dependencies :

• the one which has the "compile" scope in the pom.xml appears with a "test" scope and is therefore not added to the webapp classpath (Test scope checkbox not ticked)
• the one which has the "test" scope in the pom.xml appears without scope, which is not normal as well

However if I import the dependency project in eclipse, things go OK in the launcher :

• "classes" folder of the dependency has a "compile" scope
• "test-classes" folder of the dependency has a "test" scope

When I close the project, things revert to previous situation.

[yulvil]

This is happening with version 3.9.0. From the Dependencies tab:

pom.xml

<dependency>
    <groupId>org.apache.httpcomponents</groupId>
    <artifactId>httpclient</artifactId>
    <version>4.3.6</version>
    <scope>compile</scope>
</dependency>

<dependency>
    <groupId>org.apache.httpcomponents</groupId>
    <artifactId>httpclient</artifactId>
    <version>4.3.6</version>
    <classifier>tests</classifier>
    <scope>test</scope>
</dependency>

The workaround is to in include the "Test Scope" dependencies in the Run Configurations -> Dependencies

I peeked at the code. Does the MavenScope need to be added to the MavenDependencyInfo.equals method?