I have a large componentized build with about 20 sub-projects. As I've been moving this project to Maven I've been looking for ways to speed it up. One of the ways I've done that is setting the 'maven.junit.fork' property to 'false' to dramatically speed-up the unit-tests. However in doing this I've found that Maven, perhaps more specifically the reactor, hangs at compiling the source for the same project over and over again. I mean literally hangs. I check the process (I'm doing this on linux) and the process is doing nothing (via strace) but sucking CPU time (via top).

I've tried this with beta-8 and beta-9, using JDK 1.3.1 and JDK 1.4. The other interesting thing to note is that if I kill it (CTRL+C) and restart Maven, it picks up on the sub-project where it last hung and successfully completes to the end of the build. I'm at my wits' end here so if anyone has any suggestions or pointers I would greatly appreciate it. Oh one other thing, as an experiment I modified the 'java:compile' goal (in beta 9) so that it didn't fork a process for 'javac' and noticed that I locked-up much earlier. Maybe there's some secret process size limit that isn't allowing me to do all of this stuff in one process.

TIA

--Alex


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to