On 7/17/07, Nigel Magnay <nigel.magnay@gmail.com> wrote:
> Mostly things work, but sometimes the workspace seems to 'go bad' (starting
> a new one seems to help). For example, if create a file in a project, say,
> /WEB-INF/classes/properties.xml, and both the directories
> and the file are new, if I right-click on the project and do Team|Commit...,
> the list of files I can choose from shows only 'WEB-INF'. Successive
> checkins will then show each new directory as if it had just appeared (where
> I'd expect it to show all of them).
classes folder is usually in ignore list by default. I would not
recommend versioning that folder if this is a typical web project as a
build process might blow away the .svn folders. Usually you can put
the .xml files in a source folder and the build will copy them to
classes. That way just version them in the source folder.
> Using the team synchronize view correctly shows all the outgoing changes,
> and I can commit correctly. However, when the view updates itself after
> commit, all the directories are marked with a blue arrow to denote an
> incoming change! Doing an update doesn't of course do anything more than
> update the revision number.
This is a feature. You can turn it off if you do not need it. It
will be off by default in a future release. See:
http://markphip.blogspot.com/2006/12/subclipse-synchronize-feature-show-out.html
> I've also had very odd things happen when moving files around and committing
> - the repository seems to end up as expected, but the UI tends to be marked
> wrongly as to what things are out of sync (refresh didn't seem to help).
Not enough details to comment. Keep in mind that the svn move command
is really like svn copy + svn delete.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Jul 17 17:46:52 2007