Approach n°
1 -> +1
There is two main approaches in general for SVN (I don't know Eclipse
rule):
- You put
the branches/tags/trunk dir at the root of the repository, and projects
inside each one
- You put
the branches/tags/trunk under each sub-project (as in your eaxample)
The probleme of approach 2 is
that you can't get all
projects in one shoot: you need to go under each project, then choose
your release (branches/tags/trunk) and then got the tree.
The approach 2 is good if you consider doc, examples, plugins and test
has
completely separated sub-projects.
For me, it is not the case: trunk version of doc, examples and tests
are
related. So, I prefer approach 1 and put them under the same trunk node
in order
to be able to retrieve them in one shoot.
Just my two cents,
Cedric
TESSIER Patrick 202707 wrote:
Someone knows if ther is
an existing structure for
branches and tags in the SVN eclipse?
If not we have to decide
how to structure branches
and tags before doing the transfer.
for example I propose to
add branches and tags
for each big directory.
- branches
I'm waiting for your
opinion,
---------------------------------------------------------
Patrick Tessier
Research Engineer
DRT LIST/DTSI/SOL/LISE
CEA-Saclay
91191 Gif sur Yvette Cedex
Tel: 01 69 08 48 63
www.papyrusuml.org
---------------------------------------------------------
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev