Re: Keep regarding source folders as source folders when checking out part of project

The problem is that Eclipse imposes its own idea of project structure on
your code. It wants you to have an ear project, an ejb project, a web
project, a jar project, but there is no overarching container that
represents the entire set of projects. This isn't a Subversion problem,
it's an Eclipse problem. Eclipse doesn't play well with ANY sensible
version control system for that reason. The cvs users don't notice the
problem, because they don't have a sensible version control system. :}

Here's what works for me... create all your various Eclipse projects as
subdirectories of a top-level trunk, so you can manage them together. Use
TortoiseSVN or the command line to create the working copy of everything.
Then use File->Import to import your projects from the existing working
copy, rather than checking them out through Subclipse. When you import,
Eclipse will notice that they are already valid Subversion projects and
ask if you want to connect. Say yes.

When you need to do tagging, branching, or checkins that span multiple
Eclipse projects, use TortoiseSVN or the command line, rather than
Subclipse. That way, you can do version control transactions across your
entire project, not just the narrow window Eclipse calls a "project".

---
David Stagner
FedACH Distributed Development
Federal Reserve Bank of Minneapolis
david.stagner@mpls.frb.org
612-204-6786
"Bjarke Meier" <bm@itu.dk>
11/10/2004 11:54 AM
Please respond to users
 
        To:     users@subclipse.tigris.org
        cc: 
        Subject:        Keep regarding source folders as source folders when checking out part of 
project
Hi,
I'm quite new to Eclipse, Subversion and Subclipse. I've created a
structured project (with Trunk, Tags, Branches directories) before I heard
of Subclipse. With Subclipse I would like to check out only a part of the
(java) project - e.g. Trunk. This works perfect except for the little
tweak that Trunk isn't being checked out as a java project and thus I
cannot use my setup (with source folders and output folders for automatic
builds of class files etc).
How do I solve this problem? I would like to keep a structured project
from where I can check out Trunk or single branches/tags and use them as
independent java projects.
TIA,
Bjarke
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org