[
http://jira.codehaus.org/browse/MCOMPILER-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210186#action_210186
]
Pavel Genevski edited comment on MCOMPILER-119 at 2/22/10 8:13 AM:
-------------------------------------------------------------------
Hi Stephane,
in case the output that I attached doesn't help, I tried to analyze the build
process with JPicus to see which thread is responsible for writing those files.
In order to enable JPicus i edited mvn.bat and added this line in the beginning:
set
"MAVEN_OPTS=-javaagent:d:\jpicus.jar=trackSuccessfulDelete;trackFailedDelete"
The analysis worked fine, but I could not find these files in the snapshot. I
guess that mvn launches a number of sub processes that copy those files. Any
idea how we can enable analysis for those processes as well?
was (Author: pavel.genevski):
Hi Stephane,
in case the output that I attached doesn't halep, I tried to analyze the build
process with JPicus to see which thread is responsible for writing those files.
In order to enable JPicus i edited mvn.bat and added this line in the beginning:
set
"MAVEN_OPTS=-javaagent:d:\jpicus.jar=trackSuccessfulDelete;trackFailedDelete"
The analysis worked fine, but I could not find these files in the snapshot. I
guess that mvn lanuches a number of sub processes that copy those files. Any
idea how we can enable analysis for those processes as well?
> 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, mvn_output.log
>
>
> 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
