Community
Participate
Working Groups
Each time a new project is pulled from the CVS repository it's necessary to download all data twice, once (automatically) when sharing project (no files are written to the disk), then it's necessary to manually trigger update to actually download files to the disk. Even clicking 'update' on the 'Review and commit the project resources' screen when sharing project (earliest opportunity to do that) makes Eclipse to download data second time. All this is very time consuming on large repositories and/or slow servers.
Are you checking out or sharing. I'll assume that you are sharing a local project with an exisiting remote project as that's what your comment suggests so I'll modify the title accordingly. You assesment of the situation is correct. When sharing with an existing project, a checkout to a cached sandbox takes place in order to allow all file's whose contents match the server contents to be mark in-sync. Any remaining files are shown in the synchronize view. As you say, performing an update will refetch the contents from the server even though we have it cached locally. Although it would be possible to use the cached contents, it is not trivial. Given that performing updates in the sharing wizard is very uncommon and should only happen for a small number of files, I don't think this is a high priority though.
I gave the example of updating from the wizard as an example only - I'm not saying everyone should do it this way. What's important is to make sure data from the CVS repositories need not to be downloaded twice - exact way of achieving it is of minor importance to the end user.
Yes, I agree that in an ideal world, we would only pull the data from the server once. My point was that in 99% of the cases, we do only pull it once and the effort to make the other 1% do so is not trivial and may not be worth the effort.
Oh? :) So please, tell me, how do get the project data from CVS repository so that it's only pulled once? Each and every time, always, in 100% of cases I needed to pull all data twice (but then maybe I fall into this 1% of dumb users you mentioned ;) )
To perform a checkout from CVS, you can use the New Project or Import wizards and choose the CVS checkout wizard or you can open the repositories view and perform a Checkout or Checkout As. All of these cases basically perform a "cvs checkout".
Ok, granted, it can be done. But the fact that I had known nothing about them may indicate that your 99%/1% estimate may be wrong. There may be many more users like me who never heard about these more efficient ways of checking out data.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
