Provide option to only overwrite older files

[GoogleCodeExporter]

Hi,
And enhancement request, not a bug.

Recently we had a scenario come up that is causing us some difficulty:
Two people are working on different parts of the same project.  It's a
ColdFusion project (web scripting language) that is being developed on a
development server.  The edits take place locally, within the Eclipse
workspace, but FileSync is used to push those edits to the dev server.

When the second person does a SVN checkout, the FileSync tool pushes  
all the files in the project to the dev server, overwriting everything that
the other person has done, but hasn't yet committed to SVN.  This isn't a
huge problem because they still have the files on their local machine, but
it's inconvenient because they now have to go back and touch all their
modified files to push them back out.

I think it would be helpful if there was an option in the settings for each
synchronization mapping that allowed the user to specify if newer files
should be overwritten "always", "never", or "prompt user", and then if a
file on the dev server is newer than what was checked out from subversion
(which assumes the SVN client is setting the file date to the commit date,
rather than 'now'), it won't have to be overwritten as it currently is.

Thanks,
Jason

Original issue reported on code.google.com by jsi...@gmail.com on 14 May 2010 at 9:28

[GoogleCodeExporter]

Original comment by iloveeclipse on 15 May 2010 at 10:24

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Hello,

We had the same issue recently. Maybe it is easier for the plugin to sync only 
files that are not "out of sync" in eclipse. If you open a changed file eclipse 
asks you to refresh the file, so maybe this syncplugin could make use of that 
same functionality.

Original comment by mraaijma...@gmail.com on 27 Apr 2011 at 12:32