One of the archiving tasks (jar, zip, etc.) would probably do what you want.
Although if the project is already in CVS, a CVS update would normally be sufficient, unless you just want local copies of the changed files.
Bad phrasing. I meant to say CVS commit. One of the hardest things for me to learn about CVS is that in CVS-speak "update" means to pull updates from CVS, not put them into CVS. [ January 22, 2007: Message edited by: Tim Holloway ]
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Jan 14, 2004
My project is in CVS. I need to take local backups of my code every day(since I can check it into CVS only after my complete development). I find it a pain to manually copy the files to my local directory. Hence was planing to run a task , which would find the modified files and take a back up of the same (essentially copy it to another directory) .
The CVS Ant tasks facilitate Update , Commit etc. Is there any way whereby I can give the input of the modified files location to the Copy Task of ant , so that back up can be facilitated?
Have you considered setting up a local CVS (or subversion if you want to be trendy) instance which you can use as often as you like during development? Then, when you are ready, you can publish your changes to the other repository as normal.
I have used the "zip everything up" approach on several projects, but it's not as flexible as a real repository where you can look at changes between versions, roll back individual files or groups etc.
One of my regular complaints about version control integration in tools such as Eclipse is that they don't support this two-repository style of working.