digifork <digifork@gmail.com> wrote on 08/09/2006 10:45:27 PM:
> I just started using SVN with Eclipse and I have an issue. I have the
> following project in my SVN repository:
>
> myproj
> +-bin
> +-lib
> +-src
> +-build.xml
>
> I would like to check this project out into Eclipse as a subfolder of
> a project called "My Project". The Eclipse workspace would look like
> this:
>
> My Project
> +-.settings
> +-bin
> +-myproj
> +-bin
> +-lib
> +-src
> +-build.xml
> +-.classpath
> +-.project
>
> I like this setup because:
>
> 1. The Eclipse specific files (.settings and bin dirs, .classpath and
> .project files) are not part of the versioned source tree
> 2. If the myproj dir was the top level dir, the project would have to
> be called "myproj"
> 3. If the myproj dir was the top level dir, I would have to rename the
> output dir in my build path to something other than bin to avoid a
> conflict with my own bin dir
You cannot currently do this with Subclipse. Others have expressed
interest in attempting to add this feature, but it is too early to say
whether that will result in anything. See this thread on the dev@ list:
http://subclipse.tigris.org/servlets/ReadMsg?list=dev&msgNo=2067
Going back to your needs. You could accomplish what you want to today by
using svn:externals. Just create a place to store the Eclipse project, it
could be in you main repository if there are many programmers that need
this, or a local file:// repository if it is just you. This project would
store "My Project" and the Eclipse related files, and the "My Project"
folder would have the svn:externals property set to a value of:
myproj url://server/repos/myproj
You could then checkout "My Project" from your local file:// repository,
it would see the svn:externals and go checkout "myproj" from the other
repository (and of course it could all be the same repository too).
Also your questions/points:
1. The Eclipse specific files do not have to be versioned. If you are
not the only Eclipse programmer it is a good idea to version them though.
You can add the items to the svn:ignore property so that you do not
accidentally commit them. Or you can add them to the global Eclipse
ignored resources list.
2. Projects do not have to be the same name as the folder in the
repository. The Checkout wizard allows you to specify the Eclipse project
name.
3. This is likely true. You do not want the folder that Eclipse builds
to, to be versioned in your repository. Eclipse will occasionally
delete/recreate this folder and that will mess up your workspace. See:
http://subclipse.tigris.org/faq.html#wc-not-locked
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Aug 10 14:51:21 2006