tag:blogger.com,1999:blog-2852931951046210811.post8244238379132094666..comments2023-04-18T04:49:18.787-05:00Comments on svn commit ./me: Subclipse Synchronize Feature: Show Out of Date FoldersUnknownnoreply@blogger.comBlogger18125tag:blogger.com,1999:blog-2852931951046210811.post-77866722406477723462008-04-23T19:39:00.000-05:002008-04-23T19:39:00.000-05:00Thanks for this mate. Very helpful info. Implement...Thanks for this mate. Very helpful info. Implementing source control and tired of saying "I don't know why the icons went blue after you commited".Gatshttps://www.blogger.com/profile/16812036280210893105noreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-75114985095248327012008-04-08T14:53:00.000-05:002008-04-08T14:53:00.000-05:00I think the post already addresses your questions....I think the post already addresses your questions. When you perform commits in SVN, the revision of all parent folders is bumped in the repository causing the folder in your WC to technically be out of date. This situation then manifests as a problem if you perform an operation that requires that the folder be in synch with the HEAD revision. So this "feature" is a Subclipse feature, as the blog post heading indicates. The feature is to have Subclipse show out of date folders as incoming changes from the repository so that you can update them to the HEAD revision.Mark Phippardhttps://www.blogger.com/profile/16905022252385982106noreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-26702563437977410992008-04-08T10:21:00.000-05:002008-04-08T10:21:00.000-05:00You use the wording ‘this feature’ a few times, an...You use the wording ‘this feature’ a few times, and it is not entirely clear to me what you mean by it: the newly added feature to Subclipse, or one of the Subversion features you talk about. Could you maybe clarify this? Specifically, in the penultimate paragraph:<BR/><BR/>‘Consequently, when you would run update from this view, your folders would never get updated and would always be out of date. This feature fixes this problem, as folders now show up as changes and therefore are included in the selections.’<BR/><BR/>What is ‘this feature’ here? Yours, or the Subversion one?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-12173319038980881332008-03-12T02:16:00.000-05:002008-03-12T02:16:00.000-05:00The described feature looks like a bug. Yes, actua...The described feature looks like a bug. Yes, actually you cannot auto update folders after commit. But just don't show them by default - it will be much better for all usersAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-44611804645792882662008-02-10T16:00:00.000-05:002008-02-10T16:00:00.000-05:00Mark, I have a question regarding the topic you ad...Mark, I have a question regarding the topic you addressed in your December 19th, 2006 posting on the Subversion Move/Rename feature. Has the issue you described regarding the move/rename feature in Subversion been at all addressed since that posting in recent releases? I am currently on a project in the middle of a decision point as to which source control we should use - MS Visual Source Safe, CVS, or Subversion. Please provide any advice you can, especially as far as any update on the move/rename issue you raised in that posting. Thanks!<BR/><BR/>SabeehAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-66993559137893582422008-01-30T13:21:00.000-05:002008-01-30T13:21:00.000-05:00The revision of the folder in the repository is bu...The revision of the folder in the repository is bumped by a commit to any child location. This is a by product of the repository design and the way it "bubbles-up" a change.<BR/><BR/>The folder only needs to be at latest revision when the folder itself is being committed from your working copy.Mark Phippardhttps://www.blogger.com/profile/16905022252385982106noreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-56578989108007285582008-01-30T13:08:00.000-05:002008-01-30T13:08:00.000-05:00Why does a commit bump folder's revision, but does...Why does a commit bump folder's revision, but doesn't require an up-to-date folder? Common sense tells me it should be both or none.<BR/><BR/>I agree that automatically updating after a commit is a bad idea. So I think the solution is: if I committed a file, and its folders were up to date before the commit, then the affected local folders should be bumped 1 revision. In the rarest case when someone actually updated the folder between my check and my commit, he would also bump folder's revision, and I'm still going to see it as incoming change since I bump it +1 when it'll be at +2.rustynut1https://www.blogger.com/profile/05447262393541265566noreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-36573621524847156362008-01-19T01:02:00.000-05:002008-01-19T01:02:00.000-05:00Why not simply update after commit if there were n...Why not simply update after commit if there were no other changes?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-19760445289507929652007-07-06T08:53:00.000-05:002007-07-06T08:53:00.000-05:00It is off by default in trunk. Unfortunately, sin...It is off by default in trunk. Unfortunately, since it is a preference, this will only change it for new users/workspaces where the preferences get initialized.Mark Phippardhttps://www.blogger.com/profile/16905022252385982106noreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-16185611453429278022007-07-06T08:45:00.000-05:002007-07-06T08:45:00.000-05:00Thanks for the in-depth explanation, Mark! I defin...Thanks for the in-depth explanation, Mark! <BR/>I definitely had a hard time in understanding this new feature - and I am the most "advanced" SVN user in our company.<BR/>Like nathan and earthe, I would strongly recommend turning that feature off by default in the next release. Experts will always find the way to turn it on, all others will not understand (and not google) it.Peter Ewaldhttps://www.blogger.com/profile/06452410146070230766noreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-27737867054074429662007-06-20T12:41:00.000-05:002007-06-20T12:41:00.000-05:00I thought Subclipse was broken for a while when I ...I thought Subclipse was broken for a while when I updated Subclipse because of the new left pointing arrows in "synchronize view" after a commit. <BR/><BR/>The way Subclipse works now may be technically correct, but it just seems scary and broken to users. Maybe the pref pane where you uncheck this option should explain more or maybe it should be unchecked by default. I for one thought that the latest Subclipse was buggy.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-31751868607457794822007-05-03T07:07:00.000-05:002007-05-03T07:07:00.000-05:00It is not a bug and it is not a hack, it is the wa...It is not a bug and it is not a hack, it is the way Subversion works, and the article explains why. If you do not like it then try and convince the Subversion developers that a commit should also update your working copy.<BR/><BR/>Subversive has this exact same feature and it works exactly the same. In the same situation, they give identical results to Subclipse. The only difference is there feature is off by default and ours is on by default.Mark Phippardhttps://www.blogger.com/profile/16905022252385982106noreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-41230909336107353842007-05-03T02:35:00.000-05:002007-05-03T02:35:00.000-05:00I must concur with "earthe" regarding this issue.T...I must concur with "earthe" regarding this issue.<BR/><BR/>The "Show out of date folders" (working after restart of Eclipse) is not a good enough hack. <BR/>The revision numbers on the parent folders should be automatically updated when commiting a file - IF there are no outstanding updates in the repository along that path!<BR/><BR/>Regards<BR/>Jens Gabe<BR/><BR/>PS: The Subvesive client have no probs with this! The correct revisions are shown on the folders after a commit.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-68450132485865165132007-03-28T06:57:00.000-05:002007-03-28T06:57:00.000-05:00It is not a required update, it is information. Y...It is not a required update, it is information. You are free to ignore it, and you are free to turn off the feature.<BR/><BR/>Subversion does not do an update as part of a commit and neither does Subclipse. You would not want to receive unexpected changes from other developers as part of doing a commit. The links to the post on Mixed Revision Working Copies explains why this is so.<BR/><BR/>If you will doing a lot of move/renames or setting folder props, then I would leave the feature on as it wilk likely be helpful. Otherwise, just turn it off.Mark Phippardhttps://www.blogger.com/profile/16905022252385982106noreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-6076288877744685232007-03-28T02:14:00.000-05:002007-03-28T02:14:00.000-05:00"There really isn't any way around this. The folde..."There really isn't any way around this. The folders are out of date after a commit, so the view shows them." <BR/><BR/>I am trying Subclipse for the first time today and this 'feature' seems like a bug to me. Your text does not describe why my local folders are not automatically updated when I commit a file and the server increments the version properties on the containing folders.<BR/><BR/>As it is, this means every commit from a user results in a required update: a manual process. You're saying that the software requires a human to take multiple steps and face a UI that /seems/ to indicate someone else made a change until one takes the time to look closely at the revision history.<BR/><BR/>I'm having a hard time selling this to my users :\ Is there something built into svn that makes it impossible to know what changes "I" have caused by virtue of my own commit?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-14774883656963015792007-02-11T11:27:00.000-05:002007-02-11T11:27:00.000-05:00Thanks for making it clear for me. Was looking thr...Thanks for making it clear for me. Was looking through the issues and found it as a bug there. I always thought it was a bug because I believe in earlier test-versions it didn't work correctly when updating with the changes, seem to remember a faulty directory structure at one point. I tried now and it works - so I guess I don't have to restart Eclipse all the time anymore to get them away, yay! ;)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-83789345771850980362007-01-12T04:16:00.000-05:002007-01-12T04:16:00.000-05:00Very useful. Thanks.Very useful. Thanks.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2852931951046210811.post-80313835641242166372006-12-20T16:11:00.000-05:002006-12-20T16:11:00.000-05:00Nice post Mark, very useful information. I like th...Nice post Mark, very useful information. I like the format of the new blog too; Clean, simple and uncluttered.Paulhttps://www.blogger.com/profile/08003556403088397461noreply@blogger.com