[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Subclipse-users] Import into existing subfolder of existing project

From: parminder gupta <gupta.parminder_at_gmail.com>
Date: Thu, 20 Mar 2008 23:52:56 -0400

Hi,

First of all, thank you for finally getting Subversion support for
Eclipse. However, I have an issue that prevent me from using
Subclipse. I have been looking through available Subclipse
documentation to achieve the following. The closest thing I found was
Issue #449. I am not sure if any work has been done on that, but I
would like to present my scenario below and hopefully someone can
guide me into doing this or telling me what architectural changes are
needed in Subclipse.

I have 3 project that are in subversion with the following layout in svn://xxx/

proj_a
+---trunk
| +---File01.java
| \---File02.java
+---tags
\---branches

proj_b
+---trunk
| +---File03.java
| \---File04.java
+---tags
\---branches

proj_c
+---trunk
| +---File05.java
| \---File06.java
+---tags
\---branches

My eclipse project needs to be in the following structure, because
proj_a, proj_b and proj_c have interdependencies at the moment. There
are plans in near future to refactor the 3 projects to remove
interdependencies, thats why they have been created as 3 seperate
projects in subversion (atleast thats what i've been told). So my
eclipse layout looks like:

my_project
+---libs
+---bin
+---src
        +---com
                +---foo
                        +---proj_a [contains -> svn://xxx/proj_a/trunk/*]
                        +---proj_b [contains -> svn://xxx/proj_b/trunk/*]
                        \---proj_c [contains -> svn://xxx/proj_c/trunk/*]

I want to be able to use the plugin to checkout projects from svn into
the above structure and still be able to have complete access to all
the svn functions even if my_project (or parent folder) is not
associated with svn.

Also, in cases of projects already checked out from SVN, there should
be a simpler mechanism of tagging the project so that Subclipse would
read the folder structure, determine the presence of valid .svn/
folder & files and provide SVN support in those folders. This is what
I would consider part of basic subversion support.

Netbeans has this kind of subversion support seamlessly built-in. I am
not ready to move from eclipse simply for the lack of proper
subversion support (kinda getting around it using command line or
TortoiseSVN) but this would be a great thing to have.

Thanks,
Parminder

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-03-21 04:53:04 CET

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.