You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/06/27 21:24:10 UTC
[jira] (MNG-4633) Make weave mode work reliably
[ https://jira.codehaus.org/browse/MNG-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MNG-4633:
--------------------------------
Fix Version/s: (was: 3.x / Backlog)
> Make weave mode work reliably
> -----------------------------
>
> Key: MNG-4633
> URL: https://jira.codehaus.org/browse/MNG-4633
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 3.0-beta-1
> Reporter: Kristian Rosenvold
> Assignee: Kristian Rosenvold
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)