I have a similar issue as reported in #976 and #1154 with version 1.166 and
1.168 on Windows 2000 using Sun JVM 1.6.0_03. The problem occurs, whenever Maven
tries to checkout source files from my CVS repository using the Java CVS client
that comes with the maven-scm-plugin. As a workaround, I set the following property:

-Dmaven.scm.provider.cvs.implementation=cvs_native

which makes the build run through without any problems. Unfortunately, Hudson
runs into the same issue, when I try to execute the deploy goal. I have also
noticed that not the JVM Hudson runs in, but the VM that is spawned by
hudson.maven.agent.Main is locked up completely (i.e. it is not possible to
obtain a stack trace nor can I connect to it using jconsole).