ahh a cleanup and a refresh did the trick.
johan
On Fri, May 30, 2008 at 4:25 PM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Fri, May 30, 2008 at 10:06 AM, Johan Compagner <jcompagner_at_gmail.com>
> wrote:
> > This will result in a invalid state of things..
> >
> > First suddenly i cant update my project anymore:
> >
> > update F:/workspace/j2db_core -r HEAD --force
> > Attempted to lock an already-locked dir
> > svn: Working copy 'F:\workspace\j2db_core\build\lib' locked
> >
> > Second the jar that was deleted in this case is suddenly is an outgoing
> > change.
> > But synchronizing gives me this:
> >
> > Can't find an entry
> > svn: 'F:\workspace\j2db_core\build\lib\concurrent.jar' is not under
> version
> > control
> >
> > How can i set this straight?
> >
> > And the subclipse code should be able to handle this case a bit better i
> > guess
> > If a file that he wants to overwrite or delete because of an update. If
> that
> > doesnt work
> > he should just rollback the complete update (or just that file) and set
> that
> > one as a one that still has to be done.?
>
> Subclipse does not touch your code, we call Subversion API's and it
> does that. If there are bugs in Subversion we have to identify them
> and report them so that they can be fixed.
>
> There are cases where the Subversion Cleanup option can correct
> problems. It is at least worth a try. Usually the error message that
> Subversion outputs suggests that option when it might help though.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
> For additional commands, e-mail: users-help_at_subclipse.tigris.org
>
>
Received on 2008-05-30 16:42:58 CEST