Paul Collins <pcollins@active-sight.com> wrote on 12/19/2005 12:51:38 PM:
> I think this may be a bug in subclipse but I'm not entirely sure. I've
got a
> repository on localhost using the JavaHL interface so I can use file:///
>
> Short version:
> It appears that during the course of an update, subclipse fails to
update the
> revision number for the root directory of a project.
Subclipse doesn't update anything, JavaHL does it.
> Longer version:
> During the course of working on some python code and after doing a few
> commits, I decided to add some files to svn:ignore. That works, and then
I
> need to commit that. That commit fails because subclipse believes the
> directory is not in sync. I do an update through eclipse, try again and
get
> the same error. Figured maybe it wasn't updating the revision number for
the
> directory itself, so I do a svn up from the command line. Then from
eclipse I
> do my commit and it goes through perfectly fine.
My guess is that you are using the Synchronize view as opposed to Team ->
Update. The update behavior you describe is consistent with the behavior
of that view.
http://subclipse.tigris.org/issues/show_bug.cgi?id=403
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Tue Dec 20 05:23:38 2005