[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Current folder revision number

From: Bradley Wagner <bradley.wagner_at_hannonhill.com>
Date: 2006-06-07 22:59:04 CEST

Thanks Mark. I'm using JavaHL and doing a Team->Update manually on
the folder seemed to fix it. I take it that ideally the folder's
latest revision number is determined by the revision in which that
folder itself was last updated or something inside of it (any levels
deep) was updated correct?

Bradley

On Jun 7, 2006, at 4:50 PM, Mark Phippard wrote:

> Bradley Wagner <bradley.wagner@hannonhill.com> wrote on 06/07/2006
> 04:42:54 PM:
>
>> This may be more a Subversion, but I can only describe it in terms of
>> the Subclispe interface so here goes.
>>
>> Subclipse 1.1.1 uses Eclipse 3.2's new History view and even show's
>> the revision history for folders in my project when I select them.
>> What determines the "current" revision number for a folder? When is a
>> folder's revision number advanced? It seems like most of the folders
>> I select, their current revision in my workspace is not the latest
>> revision made to that directory and I'm not sure why. I checked to
>> see if the recent revisions were made to a different branch or tag
>> but they were all made to trunk, so I'm not sure.
>
> The revision info comes from our internal cache, which comes from
> Subversion's info in your WC.
>
> When you commit a file, the revision of the file is updated, but
> not the
> revision of the parent folders. This leads to "mixed-revision"
> working
> copies. See:
> http://svnbook.red-bean.com/en/1.0/ch02s03.html#svn-ch-2-sect-3.4
>
> The only way to get folders up to date is to explicitly update them
> using
> Team -> Update, such as selecting the project folder.
>
> There is a long-standing issue when using JavaSVN, that something
> about
> the files it touches on the disk when you do this does not trigger
> us to
> automatically update this information in our cache. A manual refresh
> fixes it. In other words, the JavaSVN update works correctly, but our
> resource change monitor does not get activated in a way that causes
> us to
> refresh our internal cache for the folders.
>
> Mark
>
>
>
> ______________________________________________________________________
> _______
> Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by
> IBM Email Security Management Services powered by MessageLabs.
> ______________________________________________________________________
> _______
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Jun 7 22:59:16 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.