After reading a number of posts about this and having had no problems
in the past with this (though it seems with each major version it
works "less"), I thought I'd add my thoughts and request a change.
To get a Java project checked out and behaving properly, I used to
use Subclipse to do a "Checkout As..." and choose "Java Project" and
everything worked as expected. It appears to have been changed to
required that Eclipse-specific resources already be in a project for
this to work, as evidenced by errors I did NOT get in previous
versions doing this same operation:
svn: File not found: revision 26, path '/trunk/.classpath'
svn: File not found: revision 26, path '/trunk/classes'
svn: Failed to add directory 'src': object of the same name
I'm guessing this is conflicts between how Eclipse creates Java
projects and what's already in the repo.
I do not agree with the opinion that you should put IDE-specific
resources in the repo unless you have a shop which absolutely has
everyone using the same software. (There are many clean non-IDE
specific ways to manage classpaths, libraries, etc, and if you're
doing nightly builds on a server you'll need to do that stuff in a
non-IDE way anyway).
Also, it seems if a project was started NOT using Eclipse then you're
stuck having to clunk around some other way to get the project
checked out and then attach Eclipse to it. This is not desirable.
In my situation this is protracted because I will often be in the
field not on my own system and need to check projects out. If I
could only install Eclipse with Subclipse to work it would be much
better than worrying about the command-line version for whatever
platform I'm on to do an initial checkout just because this feature
(in my opinion) is a bit broken.
Workaround right now is check out using command line, then create a
new Java project and point to it. Not horrible, but not as clean as
Checkout As... used to be :(
Thank you Subclipse creators!!
Received on Sat Sep 3 01:40:22 2005