You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2007/05/24 20:22:58 UTC
[jira] Created: (SUREFIRE-333) testClassesDirectory not added to
classpath
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
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
[jira] Commented: (SUREFIRE-333) testClassesDirectory not added to
classpath
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98455 ]
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 one.
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: 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.3.1
>
> Attachments: maven-surefire-plugin.patch
>
>
> 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
[jira] Updated: (SUREFIRE-333) testClassesDirectory not added to
classpath
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-333:
----------------------------------
Fix Version/s: (was: 2.4)
2.3.1
> 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.3.1
>
> Attachments: maven-surefire-plugin.patch
>
>
> 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
[jira] Updated: (SUREFIRE-333) testClassesDirectory not added to
classpath
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (SUREFIRE-333) testClassesDirectory not added to
classpath
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-333:
----------------------------------
Patch Submitted: [Yes]
> 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.3.1
>
> Attachments: maven-surefire-plugin.patch
>
>
> 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
[jira] Updated: (SUREFIRE-333) testClassesDirectory not added to
classpath
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier updated SUREFIRE-333:
-------------------------------
Attachment: maven-surefire-plugin.patch
Patch replaces classes and test-classes directories with the configured directories in the classpath.
> 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
>
> Attachments: maven-surefire-plugin.patch
>
>
> 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
[jira] Closed: (SUREFIRE-333) testClassesDirectory not added to
classpath
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed SUREFIRE-333.
---------------------------------
Assignee: Brett Porter
Resolution: Fixed
> 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
> Assignee: Brett Porter
> 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 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