You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Pavel Genevski (JIRA)" <ji...@codehaus.org> on 2010/02/11 16:06:55 UTC
[jira] Updated: (MCOMPILER-119) classes from src/main/java are
coppied to target/test-classes
[ http://jira.codehaus.org/browse/MCOMPILER-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Genevski updated MCOMPILER-119:
-------------------------------------
Attachment: effectivePom.xml
Here it is
> classes from src/main/java are coppied to target/test-classes
> -------------------------------------------------------------
>
> Key: MCOMPILER-119
> URL: http://jira.codehaus.org/browse/MCOMPILER-119
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Affects Versions: 2.0.2
> Environment: The problem occurs on both Windows and Linux
> Reporter: Pavel Genevski
> Attachments: effectivePom.xml
>
>
> When I rebuild my project I notice that main classes from src/main/java are coppied to target/test-classes. The consequence for me is that Eclipse JUnit runner uses the (possibly stale) versions of the main classes from target/test-classes. For example, if I modify a class from main JUnit runner doesn't see the changes until I do a clean rebuild of the project with maven. I checked the eclipse project export order (Properties/Java Build Path/Order and Export)and it seems OK (src/main, src/resources, src/test/java).
>
> This behavior must have been introduced recently because I checked the target/test-classes folder on a system, on which I havent ran a full rebuild recently and it only contained the test classes.
--
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