You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Nico Zimmermann <nz...@powerflasher.de> on 2006/08/16 14:46:46 UTC

Problem with ANT Sync Task

Hello List,

 

I am using the ANT-Sync task in an Eclipse/Subversion environment.

 

I synchronize two directories (both in the same SVN project) like this:

 

<sync todir=3D"test/libs/">

      <fileset file=3D"test/publish/libs/**"/> </sync>

 

Due to the sync action the .svn folder in test/publish/libs directory is
removed.

 

Now, I cannot use this project for any SVN action any more because it is
broken.

 

SVN Error---

Working copy not locked; this is probably a bug, please report

svn: Working copy 'test/publish/libs' is missing or not locked

----

 

This is correct but - is there a possibility to commit these files to
the SVN anyhow?

 

With CVS, when the cvs directory was destroyed, I could use "override
and commit".

 

Thanks for your help, Nico.


Re: Problem with ANT Sync Task

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Aug 16, 2006, at 16:46, Nico Zimmermann wrote:

> I am using the ANT-Sync task in an Eclipse/Subversion environment.
>
>
>
> I synchronize two directories (both in the same SVN project) like  
> this:
>
>
>
> <sync todir=3D"test/libs/">
>
>       <fileset file=3D"test/publish/libs/**"/> </sync>
>
>
>
> Due to the sync action the .svn folder in test/publish/libs  
> directory is removed.
>
>
>
> Now, I cannot use this project for any SVN action any more because  
> it is broken.
>
>
>
> SVN Error---
>
> Working copy not locked; this is probably a bug, please report
>
> svn: Working copy 'test/publish/libs' is missing or not locked
>
> ----
>
>
>
> This is correct but - is there a possibility to commit these files  
> to the SVN anyhow?
>
>
>
> With CVS, when the cvs directory was destroyed, I could use  
> "override and commit".

No, the .svn directory and its contents are essential to Subversion.  
Maybe you could move the .svn directory(ies) out of the way, then  
sync, then move them back so that you can commit. Of course, if this  
synchronization includes more than just changes to individual files  
(as in, includes additions or removals of files or directories) then  
you would additionally need to execute the appropriate svn add or svn  
rm commands, which would take more work to script, if that's what you  
want.

Maybe you shouldn't be using an external sync process, but rather an  
svn merge.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org