I think, if someone was able to hack something together (that worked!) and it demonstrated real added value to Maven, then the dev team would be more likely to hear this request and consider adding it. But there are so many interactions between poms, plugins, etc that I don't honestly believe it is worth the effort (which would be enormous).
So until a proof of concept is available, I think this is just a lot of chatter on the users list. The "answer" to this "problem" for me has always been "break your code up into smaller modules, and only re-compile what changed" and poof, your compile times will be drastically reduced. Wayne On 4/10/08, VELO <[EMAIL PROTECTED]> wrote: > > > > The main problem you would have with a multi-cpu build would be > > understanding the console output. Since maven isn't threaded already > > the output would be interwoven and impossible to understand. > > > > Agree... > > Will only be readable on separated text logs. > > Or multi column output (just a joke =D). > > > VELO > > > > On Wed, Apr 9, 2008 at 8:28 PM, Barrie Treloar <[EMAIL PROTECTED]> wrote: > > > On Wed, Apr 9, 2008 at 8:51 PM, Benedikt Thelen <[EMAIL PROTECTED]> wrote: > > > Hi there, i am sort of a maven newbee, > > > At our workplce we have a quite big Coccon project in developenet and > > we use > > > maven to build it. Building takes usually 5-6 minutes which is quite a > > > while. I noticed using gkrellm and htop that maven only uses one of the > > two > > > processors (Levono Thinkpad with intel core Duo) in my notebook. > > > Question: Is there a way to tell maven to use both CPU's while > > building? I > > > searched gooogle a lot but i didn't find anything. > > > > If you are building your entire system, including unit tests, in under > > 10 minutes that should be good enough. > > > > 6 minutes is fine. It gives you time to stretch your legs, go to the > > loo, grab a drink. > > > > The alternatives are: > > > > * manually select which modules to build, (i.e only the ones you > > changed) - generally it is faster to run it at the project root than > > cd around typing mvn commands > > > > * setup your IDE to use direct project references instead of > > ~/.m2/repository references - then you can develop without running > > maven at all !!!! You only run maven just prior to committing the > > changes back, which is much less often and you can afford the waste of > > 6 minutes. > > > > * turn off plugins for development and make sure they are on for > > continuous development. e.g. you may not need to run checkstyle as > > your IDE is already checking this. > > > > > > The main problem you would have with a multi-cpu build would be > > understanding the console output. Since maven isn't threaded already > > the output would be interwoven and impossible to understand. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
