Hi Nicola,
Thanks for resending, I must have missed this the first time around.
I think the most recent test is because you do not have a project checked out to the
C:\Temp directory (i.e. no CVS folders and therefore no CVS\Root folder). One
solution that might fix this is to wrap your update task in a check to see if the
project exists. Another solution would to be just to perform a checkout if the
repository does not exist, but it may clobber files if there is a mistake in your
destination attribute...so I would prefer just to error out but if there are different
opinions on this I am open to hearing them.
I think the second one might be the backslashes in the cvsroot, can you verify that
the following works from the commmandline:
C:\wincvs\cvs.exe -d:local:\\myServer\root\cvs update "-P -d"
If not you may want to try reversing the slashes (
http://www.devguy.com/fp/cfgmgmt/cvs/cvs_admin_nt.htm search for UNC Names ).
Thanks,
Clayton
-----Original Message-----
From: Nicola Iuretigh [mailto:[EMAIL PROTECTED]
Sent: Mon 10/18/2004 12:01 AM
To: [EMAIL PROTECTED]
Cc:
Subject: Re: [Nant-users] Some problems with <cvs-update> and <cvs> tasks
Any suggestion for this problem?
Thank you very much,
Nicola
----- Original Message -----
From: "Nicola Iuretigh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 15, 2004 6:29 PM
Subject: [Nant-users] Some problems with <cvs-update> and <cvs> tasks
> Hi!
>
> I am continuing with my newbie experiments...
>
> Now I'm playing with <cvs> task and related <cvs-update> and
<cvs-checkout>.
>
> When I tried to execute this task...
>
> <cvs-checkout
>
> unless="${ sourcesDestination.dir.present }"
>
> usesharpcvslib="false"
>
> destination="${ root.dir }"
> cvsroot="${ cvs.root }"
> module="${ sources.module }"
> verbose="true">
>
> </cvs-checkout>
>
>
> ... all things are ok!!
>
>
>
> Instead, when I tried <cvs-update> task with the same attributes...
>
>
> <cvs-update
>
> if="${ sourcesDestination.dir.present }"
>
> usesharpcvslib="false"
>
> destination="${ root.dir }"
> cvsroot="${ cvs.root }"
> module="${ sources.module }"
> verbose="true">
>
> </cvs-update>
>
> ... Nant told me that...
>
> [cvs-update] Working directory: C:\Temp
> [cvs-update] Executable: C:\wincvs\cvs.exe
> [cvs-update] Arguments: update -P -d
> [cvs-update] Starting 'C:\wincvs\cvs.exe ( update -P -d)' in 'C:\Temp'
> [cvs-update] cvs.exe update: No CVSROOT specified! Please use the `-d'
> option
> [cvs-update] cvs.exe [update aborted]: or set the CVSROOT environment
> variable.
> BUILD FAILED - 0 non-fatal error(s), 2 warning(s)
>
> Uhm!!??
>
>
>
> So, to finally have a cvs update, I tried this...
>
> <cvs
> if="${ sourcesDestination.dir.present }"
>
> usesharpcvslib="false"
> command="update"
> commandline="-P -d"
>
> destination="${ root.dir }"
> cvsroot="${ cvs.root }"
> module="${ sources.module }"
> verbose="true" >
>
> </cvs>
>
> And then NAnt told that...
>
>
> [cvs] Working directory: C:\Temp
> [cvs] Executable: C:\wincvs\cvs.exe
> [cvs] Arguments: -d:local:\\myServer\root\cvs update "-P -d"
> [cvs] Starting 'C:\wincvs\cvs.exe ( -d:local:\\myServer\root\cvs update
> "-P -d")' in 'C:\Temp'
> [cvs] update: invalid option --
> [cvs] Usage: cvs.exe update [-APdflRp] [-k kopt] [-r rev|-D date] [-j rev]
> [cvs] [-I ign] [-W spec] [files...]
> [cvs] -A Reset any sticky tags/date/kopts.
> [cvs] -P Prune empty directories.
> [cvs] -d Build directories, like checkout does.
> [cvs] -f Force a head revision match if tag/date not found.
> [cvs] -l Local directory only, no recursion.
> [cvs] -R Process directories recursively.
> [cvs] -p Send updates to standard output (avoids stickiness).
> [cvs] -k kopt Use RCS kopt -k option on checkout.
> [cvs] -r rev Update using specified revision/tag (is sticky).
> [cvs] -D date Set date to update from (is sticky).
> [cvs] -j rev Merge in changes made between current revision and rev.
> [cvs] -I ign More files to ignore (! to reset).
> [cvs] -W spec Wrappers specification line.
> [cvs] (Specify the --help global option for a list of other help options)
> BUILD FAILED - 0 non-fatal error(s), 17 warning(s)
>
>
>
> And now I have no more "arrows"!!!
>
> Can you help me, please?
>
>
> Thank you very much!
>
> Bye,
>
> Nicola
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Nant-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/nant-users
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
N¬HYÞéX¬²š'²ŠÞu¼ˆLúèvç-èz‰ÈLÆj«°š.®v¥RÇNšèvç-²)ò¢êÛÈzËzYn³Z·*.¶§’‡í…é÷.¬êbž*'°g·žN§gžhŸ´'«¶'âq«^°)brKh~)Ýëf¢·¡¶Úþšèvç-‚èz+fjv z»#¢êçjW(›ø.‰×®‰¨¶je5©íºÇ²f¢–)à–+-5©íºÇ²X¬¶Ë(º· ~Šàzw†Ûi³ÿåŠËl²‹«qç讧zßåŠËlþX¬¶)ßùÚÛz»
