[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mdt-papyrus.dev] How to structure branches and tags in the SVNEclipse
|
+1 for the first solution.
Thibault
TANGUY Yann 176637 a écrit :
Approach n° 1 -> +1
------------------------------------------------------------------------
*De :* mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] *De la part de* Cedric Dumoulin
*Envoyé :* jeudi 5 février 2009 14:30
*À :* Papyrus Project list
*Objet :* Re: [mdt-papyrus.dev] How to structure branches and tags in
the SVNEclipse
There is two main approaches in general for SVN (I don't know Eclipse rule):
1. You put the branches/tags/trunk dir at the root of the repository,
and projects inside each one
2. 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:
Hi,
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.
svn+ssh://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.papyrus
+doc
- branches
- tags
- trunk
+examples
- branches
- tags
- trunk
+plugins
- branches
- tags
+ trunk
-core
-uml
-other
-developer
+ test
- branches
- tags
- trunk
I'm waiting for your opinion,
Patrick
---------------------------------------------------------
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 <http://www.papyrusuml.org/>
---------------------------------------------------------
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx <mailto:mdt-papyrus.dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
------------------------------------------------------------------------
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
begin:vcard
fn;quoted-printable:Thibault Landr=C3=A9
n;quoted-printable:Landr=C3=A9;Thibault
org:Atos Origin - Agence Sud-Ouest ;Systems Integration
adr;quoted-printable;quoted-printable:5, avenue Albert Durand ;;Batiment A=C3=A9ropole ;Blagnac;Midi-Pyr=C3=A9n=C3=A9es;31701;France
email;internet:thibault.landre@xxxxxxxxxxxxxx
tel;work:+33 (0)5.34.36.34.46
note;quoted-printable:D=C3=A9veloppement durable, anticipons pour notre avenir / Sustainibility=
, advance our future=0D=0A=
P N'imprimez ce mail que si n=C3=A9cessaire / please consider your enviro=
nmental responsibility before printing this e-mail.=0D=0A=
Ce message et les pi=C3=A8ces jointes sont confidentiels et r=C3=A9serv=C3=
=A9s =C3=A0 l'usage exclusif de ses destinataires. Il peut =C3=A9galement=
=C3=AAtre prot=C3=A9g=C3=A9 par le secret professionnel. Si vous recevezc=
e message par erreur, merci d'en avertir imm=C3=A9diatement l'exp=C3=A9di=
teur et de le d=C3=A9truire. L'int=C3=A9grit=C3=A9 du message ne pouvant=C3=
=AAtre assur=C3=A9e sur Internet, la responsabilit=C3=A9 du groupeAtosOri=
gin ne pourra =C3=AAtre recherch=C3=A9e quant au contenu de cemessage.=
Bien que les meilleurs efforts soient faits pour maintenir cette transmi=
ssion exempte de tout virus, l'exp=C3=A9diteur ne donne aucunegarantie=C3=
=A0 cet =C3=A9gard et sa responsabilit=C3=A9 ne saurait =C3=AAtre recherc=
h=C3=A9e pour tout dommage r=C3=A9sultant d'un virus transmis.=0D=0A=
=0D=0A=
This e-mail and the documents attached are confidential and intended sole=
ly for the addressee, it may also be privileged. If you receive this e-ma=
il in error, please notify the sender immediately and destroy it. As itsi=
ntegrity cannot be secured on the Internet, the Atos Origin group liabili=
ty cannot be triggered for the message content. Although the sender endea=
vours to maintain a computer virus-free network, the sender does notwarra=
nt that this transmission is virus-free and will not be liable forany dam=
ages resulting from any virus transmitted.
url:http://www.atosorigin.com/
version:2.1
end:vcard
