[
http://jira.codehaus.org/browse/MNG-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230626#action_230626
]
Kristian Rosenvold commented on MNG-4633:
-----------------------------------------
Robert,
I have added an integration test to the m3 it-suite (at
https://svn.apache.org/repos/asf/maven/core-integration-testing/trunk) that
tries to reproduce your problem
(MavenITmng4633DualCompilerExecutionsWeaveModeTest). Unfortunately it only
seems to demonstrate that things work as expected.
The symptoms you describe may also arise from thread-safety issues in other
plugins. The thread safety issues in modello (fixed in 1.4) had a devastating
effect much like the one you describe here, and the symptoms may sometimes be
very strange.
Unless you can supply a test-case or test-project to demonstrate the issue, I
am not able to help you any further. While I do not doubt that you have some
kind of issue, it is almost impossible to track concurrency issues without a
real test-case.
Since the IT also demonstrates that the artifact-lock instated in r967190
works, I will close this issue. If the evidence situation should change, feel
free to re-open, or preferably create an slightly more precise issue.
Thanks
> Make weave mode work reliably
> -----------------------------
>
> Key: MNG-4633
> URL: http://jira.codehaus.org/browse/MNG-4633
> Project: Maven 2 & 3
> Issue Type: Improvement
> Affects Versions: 3.0-beta-1
> Reporter: Kristian Rosenvold
> Assignee: Kristian Rosenvold
> Fix For: 3.0-beta-2
>
>
> m3 trunk currently contains two different concurrent-build implementations;
> parallel and weave. The main target for m3 is for production quality
> "parallel" to be ready; there are numerous plugins that will need to adjust
> to this functionality.
> Alongside this activity weave mode will also be fine-tuned and evaluated; due
> to the generally tighter concurrency in this model, weave mode is more likely
> to reveal concurrency related issues in both maven, plugins, libraries and
> the jdk.
> This task is used to collect all commits related to making weave mode work
> reliably. The final evaluation of weave mode will be taken at a later stage.
> In the event that Weave mode is to be abandoned, the class
> LifecycleWeaveBuilder contains instructions on how/what can be removed from
> m3 core.
--
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
