I would like to use subversion at sourceforge for some of my projects. However, I am having real trouble getting the initial version of my code from Eclipse in my PC to the sourceforge subversion repository.
I know my Eclipse installation works with subversion at sourceforge once the project has been set up, as I have used it to work with projects created by other people. The bit I can't seem to manage is getting the code in there in the first place.
Does anyone have a pointer to a simple, step-by-step description of what I need to do? I have the svn command-line client installed if I need to use it, but naturally enough I would prefer to use the subversion client built in to Eclipse if possible.
Thanks Barry. I don't think that's quite what I'm looking for, though.
In this case I'm not transferring from an existing repository (cvs or svn). The code in question has undergone some sweeping revisions (package and class renames, class moves, etc.) and currently only exists on my PC as raw source files.
What I really want to do is create a "trunk" folder and just "slurp" my complete project directory structure into it. But I can't work out how.
I thought that you can easily create a local subversion repository with the Eclipse plug in, stuff your source into it, then dump it, then import it into Source Forge. Sorry, I did not take enough time to verify if it worked.
You should step outside of eclipse to handle the initial import. Just use the svn import command as stated on page 60 of the free svn manual:
The svn import command is a quick way to copy an unversioned tree of files into a repository, creating intermediate directories as necessary. $ svnadmin create /usr/local/svn/newrepos $ svn import mytree file:///usr/local/svn/newrepos/some/project \ -m "Initial import" Adding mytree/foo.c Adding mytree/bar.c Adding mytree/subdir Adding mytree/subdir/quux.h Committed revision 1. The previous example copied the contents of directory mytree under the directory some/project in the repository: $ svn list file:///usr/local/svn/newrepos/some/project bar.c foo.c subdir/ Note that after the import is finished, the original tree is not converted into a working copy. To start working, you still need to svn checkout a fresh working copy of the tree.
I had to explicitly enable "allow developer access to subversion" for my sourceforge user. I created the flippin' project, why would I ever not want to allow myself access to subversion.
Yeah. You are not the first one to stumble about that... :roll:
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus