[
https://jira.codehaus.org/browse/MNG-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339939#comment-339939
]
Jason van Zyl commented on MNG-4633:
------------------------------------
Kristian, feel free to reopen if you're going to work on it. But after looking
at these modes as well I only think this mode would reward poorly modularized
builds. The only time this might help is if you have a critical path where you
just can't go any further, but you really can't do a whole lot in the next
builds until the critical path finishes. This code is also super complicated.
> Make weave mode work reliably
> -----------------------------
>
> Key: MNG-4633
> URL: https://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.x / Backlog
>
>
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
