maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Gier (JIRA)" <>
Subject [jira] Commented: (SUREFIRE-333) testClassesDirectory not added to classpath
Date Tue, 05 Jun 2007 15:52:59 GMT


Paul Gier commented on SUREFIRE-333:

Thanks for including this in the next release!

I wasn't sure if the patch I made is the correct behavior for the classes and test classes
directories.  I wanted to have it work where the configured test-classes directory would be
included in addition to the default test-classes, and classes in this configured directory
would take priority over the default in the class path.  But when I tried it, the default
path seemed to always take priority (when two classes have the same name) over the configured

So I ended up just having the configured directories, if present, replace the default path
in the classpath.  Hopefully this is ok.

> testClassesDirectory not added to classpath
> -------------------------------------------
>                 Key: SUREFIRE-333
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Improvement
>         Environment: Maven 2.0.6, Fedora Core 6
>            Reporter: Paul Gier
>             Fix For: 2.3.1
>         Attachments: maven-surefire-plugin.patch
> When I change  the testClassesDirectory, these classes don't appear to be added to the
> I want to be able to compile test classes to the standard test-classes directory, then
modify the classes and put the modified classes into another directory.  Currently when I
try to do this, the original test-classes are being picked up from the class path, and not
the modified classes.
> Ideally the original test-classes directory should not be included in the classpath if
I specify a value for testClassesDirectory.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message