You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/05/25 02:51:58 UTC
[jira] Updated: (SUREFIRE-333) testClassesDirectory not added to
classpath
[ http://jira.codehaus.org/browse/SUREFIRE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-333:
----------------------------------
Fix Version/s: 2.4
> testClassesDirectory not added to classpath
> -------------------------------------------
>
> Key: SUREFIRE-333
> URL: http://jira.codehaus.org/browse/SUREFIRE-333
> Project: Maven Surefire
> Issue Type: Improvement
> Environment: Maven 2.0.6, Fedora Core 6
> Reporter: Paul Gier
> Fix For: 2.4
>
>
> When I change the testClassesDirectory, these classes don't appear to be added to the classpath.
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira