The following issue has been updated:
Updater: John McKeown (mailto:[EMAIL PROTECTED])
Date: Tue, 3 Feb 2004 7:37 AM
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.
Changes:
Attachment changed to ModifiedTestGoal.txt
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPTEST-16&page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPTEST-16
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPTEST-16
Summary: Test Plugin should support additional classpath entries
Type: New Feature
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-test-plugin
Assignee: Jason van Zyl
Reporter: Steffen Dingel
Created: Mon, 1 Dec 2003 4:45 AM
Updated: Tue, 3 Feb 2004 7:37 AM
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).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
