Hi Merrill,
 
I was unable to replicate either issue you have reported below.  These are the steps I 
went through to try to replicate them, so please fill in the details if there are 
additional steps along the way (please note I used the nant repository to checkout 
from and am running on a Windows machine):
     1) did a fresh checkout of NAnt using the <cvs-checkout /> task:
    <target name="checkout">
        <cvs-checkout 
            destination="E:\test\nant\merrill\working" 
            cvsroot=":pserver:[EMAIL PROTECTED]:/cvsroot/nant" 
            password="" 
            module="nant" />
    </target>
 
    2) Set the global override to use a non-sharpcvslib binary:
    <property name="sourcecontrol.usesharpcvslib" value="false"/>
 
    3) Used the <cvs-update/> task to update the sources I just checked out:
    <target name="update">
        <cvs-update 
            destination="E:\test\nant\merrill\working\nant" 
            cvsfullpath="C:\Program Files\TortoiseCVS\cvs.exe"
            cvsroot=":pserver:[EMAIL PROTECTED]:/cvsroot/nant" 
            password="" 
            module="nant" />
    </target>

If you went through the same steps can you please use:
     nant -help
 
NAnt 0.85 (Build 0.85.1650.0; net-1.1.win32; nightly; 08/07/2004)
Copyright (C) 2001-2004 Gerry Shaw
NAnt Team
 
and report your version number (including build date) of the NAnt nightly that you are 
using.  If it is not the most recent you may consider grabbing the most recent and 
reporting back.  Also can you also run a:
    cvs --version
 
to see what version of the cvs binary you are using?  I imagine that if you are using 
the latest nightly build and you run the command:
    cvs update -Pd 
 
on your checked out project folder that you will get an "in the way error" as well.  
Checking out your sources into a fresh directory might be a good thing.  Please let me 
know what you find.
 
 
Cheers,
 
 
Clayton
 

        -----Original Message----- 
        From: Merrill Cornish [mailto:[EMAIL PROTECTED] 
        Sent: Thu 08/07/2004 8:44 AM 
        To: [EMAIL PROTECTED] 
        Cc: 
        Subject: [Nant-users] Is <cvs-update> Really <cvs-checkout>
        
        

        I am starting a new NAnt script using the 0.85 nightly build, and I'm having 
trouble with the <cvs-update> task.
        
        The first problem (which was actually with <cvs-checkout>) is that the 
built-in Sharp CVS library didn't recognize my cvsroot argument of ":pserver:[EMAIL 
PROTECTED]:/ext/xxx".  The error message said that userid "xxxbldr" was unknown or the 
password was wrong.  However, both cvsroot and cvspassword were the same values I had 
use successfully (cut and pasted) for NAnt 0.84 scripts.
        
        I set the sourcecontrol.usesharpcvslib property to false and let it find 
cvs.exe from WinCvs 1.3 in my path--and it worked.
        
        Having found a CVS that would work with 0.85, I tried <cvs-checkout>, and it 
worked as advertised.  However, checking out on top of a previous checkout resulted in 
a bunch of "move away xxx; it is in the way" messages as it should.  So, I tried doing 
a <cvs-update> with the same arguments, expecting it to quickly determine that there 
was nothing that needed updating.
        
        Instead, I got all those "it is in the way" messages again.  Examining the 
output, the <cvs-update> log entries are prefixed with "[cvs-checkout]" labels.  It 
appears that the following:
        
             <cvs-update cvsroot="${cvsroot}" password="${cvspswd}" 
destination="${buildroot.parm}"
                                module="xxx" />
        
        is really executing <cvs-checkout>
        
        Merrill
        
        
        -------------------------------------------------------
        This SF.Net email sponsored by Black Hat Briefings & Training.
        Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
        digital self defense, top technical experts, no vendor pitches,
        unmatched networking opportunities. Visit www.blackhat.com
        _______________________________________________
        Nant-users mailing list
        [EMAIL PROTECTED]
        https://lists.sourceforge.net/lists/listinfo/nant-users
        

Reply via email to