Eclipse: Version: 3.4.2 Build id: M20090211-1700
Subclipse: 1.6.x? Integration 3.0.0, Client 1.6.2, JavaHL 1.6.0.1, (...rest
avail on request. Uh guys, on planet earth, one revision number per product
release is considered a nice touch...)
Reproduced on 2 different projects.
Steps to repro:
Create new project in eclipse with some files in it. Mine was called
"FractalGenerator"
Create svn repository on server called "dev", call it "depot."
Create svn directory, call it "art."
Under art, create 3 svn subdirectories: branches, tags, trunk.
We're gonna try to import the "FractalGenerator" project under the
"art/trunk" directory in the depot.
Select FractalGenerator project in eclipse, right click project name in
eclipse project explorer.
Select "Team" -> "Share Project..." -> SVN (as opposed to CVS) -> Next...
Use existing repository location (svn://dev/depot) -> Next...
Select "Use specified folder name" radio button, select Select... button
Browse in "Repository Browser" for "art/trunk" select OK.
"Use specified folder name" is now populated with
"art/trunk/FractalGenerator", and "URL" is now populated with:
"svn://dev/depot/art/trunk/FractalGenerator"
This all looks peachy - looks like it should work. -> Next...
Add descriptive comment. -> hit Finish
Console output:
- - - - - - - - - -
Filesystem has no item
svn: URL 'svn://dev/depot/art/trunk/FractalGenerator' non-existent in that
revision
mkdir --parents -m "Initial import from 1-4-2009 archive."
svn://dev/depot/art/trunk/FractalGenerator
checkout svn://dev/depot/art/trunk/FractalGenerator -r HEAD
--depth=immediates --force
Checked out revision 10.
- - - - - - - - - -
At the end of this, there is a "FractalGenerator" directory under "trunk" in
the repository, but it has no files under it.
The FractalGenerator project on my local filesystem has an .svn directory,
but none of the subdirectories do.
The eclipse project explorer shows the little asterisk thingy in the
FractalGenerator icon, but all the project folders and files have sad little
blue question marks on them.
Workaround:
Manually clicked on my "src" and "test" packages in eclipse project
explorer, right click, select Team -> "Add to revision control"
The files get happily added in and their little question marks get replaced
by blue thingys that seem to indicate their ready to go into the repository.
Right click project again and select "commit" and everything comes up
including the .project and .classpath files that still have the little
question marks. Deselected those in case they cause trouble with the commit,
added snide comment about subclipse screwing up the import, and commit - now
it's mostly happy. I'm concerned about the future with the .project and
.classpath files hanging out w/no version control.
console output:
- - - - - - -
commit -m "Completing the initial import that subclipse screwed up." (25
paths specified)
...(file names)
Transmitting file data ...
Committed revision 11.
- - - - - - -
Also tried on another project just importing the files directly using the
"SVN Repositories" view. (new remote folder, import..., import direct from
file system)
It imports it into the svn repository like a champ, no weird error messages.
But, this isn't as nice because now the project is not under version control
and needs to be checked out. You have to check it out over itself, and hope
nothing screwed up. So far it seems OK.
This is not the user experience I was hoping for. Hope you guys can find and
fix the problem.
Thanks,
- John
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2353370
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-05-25 02:18:56 CEST