hi, I totally agree about parallizing the build process of unrelated artifacts.
my 5cents on this one: I imagine a not so distant future were I can tell my continuous integration system that I want to build a maven project on a cluster. Maven (or the CI) should be able to separate unrelated artifacts and build them in parallel, to break down the build time. Simone Gianni-2 wrote: > > VELO wrote: >>> On the build process itself, it has no meaning to parallelize it as you >>> properly pointed out. >>> >>> >> >> May this is true on Java... >> >> But on flex is not. Flex compilation always use 100% on a single core >> computer and never use more them 50% on multi core. >> >> Well, if we got downloads and tests multithreaded I will be very very >> happy >> =D >> > Hi Velo, > yes, you are right. I was referring to "build process" as the steps and > phases Maven takes while building, one of which is "compile the > sources". If the "compile" step is single threaded or multi threaded > obviously changes depending on the compiler maven invokes. > > Simone > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Multiple-CPUs-tp16584814s177p16674687.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
