Test Plugin should support additional classpath entries

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: None
  • Fix Version/s: 1.8
  • Labels:
    None

Description

When running tests, it is sometimes required to have JARs in the classpath which are not required to compile the project or the test classes (for example a JDBC driver JAR). This should not be in the dependency list in project.xml. Therefore I suggest adding a propertery "maven.test.addionalPath" to configure such JARs. This can be easily implemented by adding a line

<pathelement path="${maven.test.additionalPath}"/>

to the classpath in plugin.jelly (line 112 in the RC1 revision).

Issue Links

is duplicated by

Improvement - An improvement or enhancement to an existing feature or task. MPTEST-47 It should be possible to add additional elements to the test classpath

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
dion gillard added a comment -

I'd much rather we add a <category> to the <dependency>

Show
dion gillard added a comment - I'd much rather we add a <category> to the <dependency>
Hide
Permalink
John McKeown added a comment -

I have encountered a similar problem. I am working on a project that loads runtime configuration files using the system ClassLoader. This requires the folder containing the configuration files to be in the classpath. When I run the unit tests through Maven I would like to include the folder in the classpath for the junit task so that the classes being tested have access to the configuration files.

I assumed this could be resolved by passing JVM arguements to the Test Plugin using the 'maven.junit.jvmargs' property. However if this property contains entries for -classpath or -cp they will be effectively ignored because a seperate classpath is added to the junit task which will override both of these. If the goals in the Test plugin were modified to recognise classpath/cp entries specified as JVM arguments then additional pathelements could be included in junit task by simply changing the project.properties file.

See attached for an example of how this could be done.

Show
John McKeown added a comment - I have encountered a similar problem. I am working on a project that loads runtime configuration files using the system ClassLoader. This requires the folder containing the configuration files to be in the classpath. When I run the unit tests through Maven I would like to include the folder in the classpath for the junit task so that the classes being tested have access to the configuration files. I assumed this could be resolved by passing JVM arguements to the Test Plugin using the 'maven.junit.jvmargs' property. However if this property contains entries for -classpath or -cp they will be effectively ignored because a seperate classpath is added to the junit task which will override both of these. If the goals in the Test plugin were modified to recognise classpath/cp entries specified as JVM arguments then additional pathelements could be included in junit task by simply changing the project.properties file. See attached for an example of how this could be done.
Hide
Permalink
dion gillard added a comment -

Why not just add <unitTest><resources> to your project.xml?

Show
dion gillard added a comment - Why not just add <unitTest><resources> to your project.xml?
Hide
Permalink
Steffen Dingel added a comment -

<unitTest><resources> does not allow adding JARs to the classpath. It works when we unpack the JARs and add the directories to <unitTest><resources>, but that is not a very convenient solution.

Show
Steffen Dingel added a comment - <unitTest><resources> does not allow adding JARs to the classpath. It works when we unpack the JARs and add the directories to <unitTest><resources>, but that is not a very convenient solution.
Hide
Permalink
thierry lach added a comment -

I think it would be more useful to allow dependencies to declare which classpaths they should be used in (default would be in all). Then the pom would provide the configuration.

Show
thierry lach added a comment - I think it would be more useful to allow dependencies to declare which classpaths they should be used in (default would be in all). Then the pom would provide the configuration.

People

  • Assignee:
    Lukas Theussl
    Reporter:
    Steffen Dingel
Vote (2)
Watch (5)

Dates

  • Created:
    Updated:
    Resolved: