Thanks...I will try that.

Is there a particular reason why there isn't a specific <cvs-commit>
task? 

>-----Original Message-----
>From: Clayton Harbour [mailto:[EMAIL PROTECTED] 
>Sent: Tuesday, December 14, 2004 8:47 AM
>To: Morris, Jason; [EMAIL PROTECTED]
>Subject: RE: [Nant-users] <cvs> task question...How to add a comment?
>
>Hi Jason,
>
>Try using the commandline attribute and passing your message 
>in that way.  So:
>
>    <cvs usesharpcvslib="false" command="commit" 
>commandline="-m &quot;${my.comment}&quot;">
>       <fileset>
>         <include name="build.number"/>
>       </fileset>
>    </cvs>
>
>
>Cheers,
>
>Clayton
>
>> -----Original Message-----
>> From: Morris, Jason [mailto:[EMAIL PROTECTED]
>> Sent: December 13, 2004 8:41 AM
>> To: [EMAIL PROTECTED]
>> Subject: RE: [Nant-users] <cvs> task question...How to add a comment?
>> 
>> 
>> I thought I tried that, but I went and tried it again still got an 
>> error.
>> 
>> The problem is that the <arg> values get placed before the 
>"commit" in 
>> the cvs command line and this is not a valid command line 
>for the cvs 
>> client.
>> 
>> Invalid cvs command line is:
>> 
>>      cvs.exe -q -x -m "my.comment" commit "build.number"
>> 
>> And the valid one is:
>> 
>> cvs.exe -q -x commit -m "my.comment" "build.number"
>> 
>> I tried to add the '-m "my.comment"' to the command attribute, but I 
>> think there is a validator that is checking for valid commands.
>> 
>> Jason
>> 
>>       [cvs] Using ssh binary:
>>       [cvs] Using .cvspass file:
>>       [cvs] Working directory: C:\projects\wiki
>>       [cvs] Executable: C:\Program Files\TortoiseCVS\cvs.exe
>>       [cvs] Arguments:  -q -x -m "my.comment" 
>-d:sspi:ocsccsdcvs01:/wiki commit "build.number"
>>       [cvs] Starting 'C:\Program Files\TortoiseCVS\cvs.exe ( 
>-q -x -m 
>> "my.comment" -d:sspi:ocsccsdcvs01:/wiki commit "build.number")' in 
>> 'C:\projects\wiki'
>>       [cvs] C:\Program Files\TortoiseCVS\cvs: invalid option -- m
>>       [cvs] Usage: cvs [cvs-options] command 
>> [command-options-and-arguments]
>>       [cvs]   where cvs-options are -q, -n, etc.
>>       [cvs]     (specify --help-options for a list of options)
>>       [cvs]   where command is add, admin, etc.
>>       [cvs]     (specify --help-commands for a list of commands
>>       [cvs]      or --help-synonyms for a list of command synonyms)
>>       [cvs]   where command-options-and-arguments depend on 
>> the specific
>> command
>>       [cvs]     (specify -H followed by a command name for
>> command-specific help)
>>       [cvs]   Specify --help to receive this message
>>       [cvs]
>>       [cvs] The Concurrent Versions System (CVS) is a tool 
>for version 
>> control.
>>       [cvs] For CVS updates and additional information, see
>>       [cvs]     the CVSNT home page at http://www.cvsnt.org/
>> 
>> BUILD FAILED - 0 non-fatal error(s), 14 warning(s)
>> 
>> >-----Original Message-----
>> >From: Troy Laurin [mailto:[EMAIL PROTECTED]
>> >Sent: Sunday, December 12, 2004 12:00 AM
>> >To: Morris, Jason
>> >Cc: [EMAIL PROTECTED]
>> >Subject: Re: [Nant-users] <cvs> task question...How to add 
>a comment?
>> >
>> >Jason,
>> >
>> >Have you tried moving your comment to an argument element: <cvs 
>> >usesharpcvslib="false" command="commit">
>> >   <fileset>
>> >     <include name="build.number"/>
>> >   </fileset>
>> >   <arg line="-m ${my.comment}" />
>> >   <arg line="-q -x" />
>> ></cvs>
>> >
>> >If your comment has spaces in it, then the argument may need to be 
>> >escaped:
>> ><arg line="-m &quot;${my.comment}&quot;" />
>> >
>> >
>> >-T
>> >
>> >
>> >Morris, Jason wrote:
>> >> I am trying to commit my build.number file after using the
>> <version>
>> >> task.
>> >> 
>> >> I can successful do a <cvs-update> on my file, but I cannot
>> >commit it
>> >> without the comment editor popping up.  All attempts at
>> >getting the -m
>> >> "comment" on the command line haven't been successful.
>> >> 
>> >>          <cvs usesharpcvslib="false" command="commit -m
>> >${my.comment}">
>> >>               <fileset>
>> >>                      <include name="build.number"/>
>> >>               </fileset>
>> >>           <arg line="-q -x" />
>> >>          </cvs>
>> >> 
>> >> I would like to get ${my.comment} added, but if I can 
>suppress the 
>> >> comment editor from popping up, I will take that as well.
>> >> 
>> >> Using CVSNT client (2.0.51d) packaged with TortoiseCVS 1.8.7.
>> >> 
>> >> Any suggestions?
>> >> 
>> >> Jason
>> >> 
>> >> 
>> >> -------------------------------------------------------
>> >> SF email is sponsored by - The IT Product Guide Read
>> honest & candid
>> >> reviews on hundreds of IT Products from real users.
>> >> Discover which products truly live up to the hype. Start
>> >reading now.
>> >> http://productguide.itmanagersjournal.com/
>> >> _______________________________________________
>> >> Nant-users mailing list
>> >> [EMAIL PROTECTED]
>> >> https://lists.sourceforge.net/lists/listinfo/nant-users
>> >> 
>> >
>> >
>> 
>> 
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide Read honest & candid 
>> reviews on hundreds of IT Products from real users. Discover which 
>> products truly live up to the hype. Start reading now.
>> http://productguide.itmanagersjournal.com/
>> _______________________________________________
>> Nant-users mailing list
>> [EMAIL PROTECTED]
>> https://lists.sourceforge.net/lists/listinfo/nant-users
>> 
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to