Markus Karg wrote:
> okay, so I have checked with the command line tool: cvs status tells
> me some interesting things:
> (a) .classpath and .project are marked with a question mark. Actually
> those files are hidden in the Java perspective since they are Eclipse
> internal stuff. Subclipse seems to not know about the fact that those
> are not user's source code?
> (b) Same happens for the folder 'bin'. Actually I cannot see that
> folder in the Java project since Eclipse handles that folder internally.
> (c) One file was changed from lowercase to uppercase. Subclipse keeps
> that file marked as "to be deleted" when doing svn status.
> The reason for all of that might be (again) that the project was
> stored in Microsoft's VSS before: VSS doesn't care for
> upper/lowercase. After manually putting the source into SVN by the svn
> command line tools, in Eclipse I just disconnected the project from
> VSS and then did "Team/ShareProject/SVN". Maybe this was the wrong
> way? I didn't want to clear the sources locally, but maybe doing that
> and afterwords doing a new checkout would have prevented this.
Most of this stuff is covered in various FAQs and documentation for both
subversion and subclipse.
I liked the subversion book. Just the fact that it was there was kewl.
The bit about deleteing the
renamed file is odd I think. Did the command SVN say the same thing?
Some people like to save .project and such (not bin, probably) in the
repository. Unless you add
the file to svn:ignore it will come up as being needed to be committed.
to quote Marc:
-1. An unversioned but not svn:ignore-d file is dirty -- action needs
to be taken on that folder.
If you want to suppress the dirty flag for that file, you should
You probably don't want to commit any directory that eclipse regularly
deletes, as the .svn folder
with all the metadata will get deleted as well.
I'm getting sleepy, so I could be wrong;
Like my email's formatting... :-)
Received on Fri Sep 30 19:11:57 2005