subclipse and the trunk/tags/branches structure

Hello,

Currently I'm in the proces to replace CVS with SVN at work. I'm using
the subclipse plugin now, which is great. I don't know when synchronize
will work but I think we can manage without it for now.

The way we have set up CVS is that we have a repository with modules for
each project. I've set up SVN to use one repository "java". So I use the
repository http://svnserver/java. From Eclipse I create new modules with
subclipse to this repository, eg http://svnserver/java/module.

After I've created the module, I know create three branches: trunk, tags
and branches. Then I switch to the trunk and add the code for that
project to the trunk. Is that the common way to get a subclipse project
into a trunk/tags/branches structure?

The "problem" with this is that I sometimes forget to switch to trunk
and add all code to the main module directory. Then I'll have to move
the code to the trunk by hand. Also I have to educate other users to use
SVN/subclipse and I think those people will make the same mistake for
sure :)

Would it be possible for subclipse to create the trunk, tags and
branches on initial module creation and switch to trunk? Or are there
other ways to accomplish the things I'm doing now? (or maybe I'm missing
some points)

Thanks,

Hugo
Received on Mon Jan 24 08:19:43 2005