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

Re: [Subclipse-users] Modified files decorated as not being under revision contr

From: techtonik <techtonik_at_php.net>
Date: 2007-09-04 09:27:54 CEST

On 9/3/07, Mark Phippard <markphip@gmail.com> wrote:
> On 9/3/07, techtonik <techtonik@php.net> wrote:
> > Build directory is under revision control and when Eclipse regenerates
> > some binary files inside, subclipse 1.2.4 behaves very strange about
> > these changes. There is no decorator placed next to file icon although
> > "Managed" and "Modified" attributes for this file are set to 'true'.
> > File doesn't appear in commit dialog for the same reason. Command line
> > 'svn st' reveals no anomaly in working copy structure.
> In general it is bad practice to store a build folder in version
> control, and Eclipse in particular makes it even worse because of all
> the auto-building it does. Also, an Eclipse team provider will not
> perform versioning operations on files produced by Eclipse compilers.
> These files are marked as Derived within Eclipse and team providers
> are instructed to ignore those files automatically, which we do.

Thanks for detailed explanation.
I use build folder to synchronize web project with production server
and find it very convenient practice. I can't name any reasons why it
could be considered bad to use SVN for updating files, to switch
branches and quickly rollback in case something goes wrong.

Is it possible to provide an option or a hack to make our team
provider recursively ignore Derived attribute for certain folders?

--anatoly t.
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Sep 4 09:24:45 2007

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.