[
http://jira.codehaus.org/browse/MNG-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219340#action_219340
]
Christian Gleissner commented on MNG-3004:
------------------------------------------
This feature works very well and resulted in a significant build time
reduction, depending on the number of cores. Why was the output de-multiplexer
commented for Maven 3 Beta 1 and when will this very useful feature be
re-enabled?
Also, when performing a parallel build, TeamCity 5's automatic collection of
Maven Surefire results no longer finds all results. We are using an external
invocation of Maven 3. This may be related to how TeamCity checks for the
completion of modules by scanning the log file and could go away once the
output de-multiplexing will be re-enabled.
> Allow build lifecycle to execute projects in parallel
> -----------------------------------------------------
>
> Key: MNG-3004
> URL: http://jira.codehaus.org/browse/MNG-3004
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Bootstrap & Build, General, Performance
> Affects Versions: 2.0.6
> Reporter: Nigel Magnay
> Assignee: Kristian Rosenvold
> Fix For: 3.0-beta-1
>
> Attachments:
> MNG-3004-Resurrected-StringSearchModelInterpolatorTest.patch,
> MNG-3004.increased-testability.patch, MNG3004-SSMI.patch, mng3004.patch,
> mng3004v2_rev2.patch, parallel-builds.patch
>
>
> One of the great advantages with maven over scripted build environments is
> that it can calculate the dependencies of the build, and it could execute
> items that are independent of each other in parallel.
> Unfortunately it currently doesn't do this, which would be a big win over
> tools such as 'ant'. It also means that multicore machines have lots of idle
> capacity when running a serial build that could be utilised.
> I had a quick shot at seeing what might be required. Bear in mind this is the
> first time I have looked at maven internally, and I was just trying to feel
> my way around and build a POC. I got some of the way there, but my build
> threads don't seem to have the correct classpath - I think this is something
> to do with plexus / classworlds - but I don't know enough.
> It'd be great to get this feature in a future version, or a way of running my
> hack (figuring out why in a thread has not the plexus stuff) in the interim.
--
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
