Ant Cannot Run Program Cvs Createprocess Error=2
Comment 4 ncrowdy 2009-02-24 18:41:50 UTC You're absolutely correct and please accept my apologies for wasting your time. Join Now For immediate help use Live now! The intention is to suppress the "24 more ..." line at the bottom of the trace. There are actually several answers to this question. weblink
build.succeeded.notify=true [email protected] build.succeeded.email.subject=Nightly build succeeded! Mark Melvin wrote: > No takers on this one? Here is the start of the second paragraph on the cvs task: Important: This task needs "cvs" on the path. Gee - I was hoping all of my problems would magically be solved this weekend by the Ant-with-CVS-gnomes. ;o) Oh well, back to it... http://stackoverflow.com/questions/10299645/ant-complains-about-cannot-run-program-cvs
It works only if I have CVS_HOME set on Windows path (PATH=c:\cvs), otherwise it returns a error: Error: build.xml:60: java.io.IOException: Cannot run program "cvs" (in directory "C:\antTest\cntl"): CreateProcess error=2 line 60 You can get at a hashtable with all the properties that Ant has been using through the BuildEvent parameter. The doc says it must be version 1.10 or higher - and the Tortoise cvs.exe is version 2.0.11 so I figured I was OK.
However, I am really confused that why I need to install CVS client if I can check out and check in and other cvs operations through eclipse's default CVS client facility. In January 2000, Ant was moved to a separate CVS module and was promoted to a project of its own, independent of Tomcat, and became Apache Ant. So.. If the value represents a file path, like a jar needed to compile, the task which requires the value, javac for example would fail to compile since it can't find the
The root of the problem is that the class that needs the external library is on the CLASSPATH. You have to start "cmd" instead and use "start" as first argument. I use ssh and everything works fine from the command line. With Ant 1.7.0 we've started to add ant-testutil.jar as part of the distribution and this causes a hard dependency on JUnit - at least in version 1.7.0.
The possible solutions depend on the version of Ant you use, see the next sections.