I noticed a similar issue even though I'm using JavaHL. Yesterday, I
was examining some outgoing changes in Synchronize View, and then I
committed them using the command line client. When I re-syncrhonized,
Subclipse didn't seem to realize that the commit happened, and still
showed those files as outgoing... I'm pretty sure this wasn't the case
On Wed, 2006-12-13 at 16:26 +0100, Martin Burger wrote:
> I use version 1.1.9 of Subclipse on my Mac OS machine. Subclipse is
> configured to use SvnKit as interface to Subversion.
> Since upgrading to 1.1.9 I have the following problem: the label
> decorations are not updated properly after a commit with an external
> client (SmartSVN).
> For example: (1) I change some files in Eclipse. The icons next to the
> changed files indicate modifications. Right. (2) I commit these changes
> with SmartSVN. So, Subclipse does not know anything about that commit.
> (3) Back in Eclipse, I refresh my project to "inform" Subclipse about
> the recent commit.
> Now, the icons showing modifications should turn into "normal" icons.
> But: The icons still indicate modifications. If I want to commit these
> "modifications" in Eclipse, Subclipse will say "No files were
> changed..". ¡Claro que sí! I just committed via SmartSVN.
> A teammate has a very similar problem: He uses svn on command line.
> After committing changed files and refreshing the corresponding project,
> the icon next to the files does not show a modification anymore, but the
> parent folder (Java package) indicates changed files - but, there are no
> changed files.
> See: http://subclipse.tigris.org/issues/show_bug.cgi?id=592
> What could be the defect causing that failure?
> Regards, Martin
> To unsubscribe, e-mail: email@example.com
> For additional commands, e-mail: firstname.lastname@example.org
NOTICE: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information of Motricity. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Received on Wed Dec 13 16:29:51 2006