I have destroyed empty /svnroot/modeling/org.eclipse.mdt.papyrus/org.eclipse.papyrus.releng
I will destroy svnroot/modeling/org.eclipse.mdt.papyrus/trunk/plugins/others/org.eclipse.mdt.papyrus.releng
as soon as the psf files proposed by Javier are commited and updated to point
to the good releng project.
---------------------------------------
Rémi
SCHNEKENBURGER
+33 1
69 08 48 48
CEA LIST, Boîte courrier 65,
F-91191 Gif sur Yvette Cedex
---------------------------------------
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De
la part de Emilien PERICO
Envoyé : lundi 7 décembre
2009 11:53
À : Papyrus
Project list
Objet : Re: [mdt-papyrus.dev]
Updating psf files
Maybe we should delete the one into others repository
SCHNEKENBURGER Remi 211865
a écrit :
Small fix:
/modeling/org.eclipse.mdt.papyrus/trunk/org.eclipse.papyrus.releng
---------------------------------------
Rémi
SCHNEKENBURGER
+33 1 69
08 48 48
CEA LIST, Boîte courrier 65,
F-91191 Gif sur Yvette Cedex
---------------------------------------
Ok for me, it worked with
my subversive plugin.
The only thing is that
the releng project is not the one placed in
svnroot/modeling/org.eclipse.mdt.papyrus/trunk/plugins/others/org.eclipse.mdt.papyrus.releng,
but rather /svnroot/modeling/org.eclipse.mdt.papyrus/org.eclipse.papyrus.releng
(root of the papyrus svn repository).
Regards,
Remi
---------------------------------------
Rémi
SCHNEKENBURGER
+33 1
69 08 48 48
CEA LIST, Boîte courrier 65,
F-91191 Gif sur Yvette Cedex
---------------------------------------
Are all of you ok with
this psf file?
Attached you can find a psf file with the latest state
of the repository created with Subversive.
If this file works for everyone it can taken as base on which to perform psf
changes.
Regards;
Javier Cano
--
Cedric Dumoulin
wrote:
One problem is that some use subclipse (from Tigris) and other subversive
(from Eclipse), and the exported .psf seem to be not compatible ...
Cedric
Francisco Javier Cano wrote:
Hello,
the psf files are outdated as new plugins have been added and old ones have
been removed.
Is there any policy on when and how to update the psf?
If not, I propose that whenever someone adds or removes a plugin that same
committer updates the psf.
Regards,
Javier
--
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
--
Francisco Javier Cano Muñoz
Programador senior del Proyecto MOSKitt
![](jpgJw1QXkf5Bs.jpg)
-----------------------------------------------------
Prodevelop S.L.
Don Juan de Villarrasa 14, 5
e-mail: fjcano@xxxxxxxxxxxxx
Tel: (+34) 963510612
![](gifMODNVTVosD.gif)
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
--
Développement
durable, anticipons pour notre avenir / Sustainibility, advance our future
P N'imprimez ce mail que si nécessaire /
please consider your environmental responsibility before printing this
e-mail.
|
Ce message et les pièces jointes
sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il
peut également être protégé par le secret professionnel. Si vous recevez ce
message par erreur, merci d'en avertir immédiatement l'expéditeur et de le
détruire. L'intégrité du message ne pouvant être assurée sur Internet, la
responsabilité du groupe Atos Origin ne pourra être recherchée quant au
contenu de ce message. Bien que les meilleurs efforts soient faits pour
maintenir cette transmission exempte de tout virus, l'expéditeur ne donne
aucune garantie à cet égard et sa responsabilité ne saurait être recherchée
pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail in
error, please notify the sender immediately and destroy it. As its integrity
cannot be secured on the Internet, the Atos Origin group liability cannot be
triggered for the message content. Although the sender endeavours to maintain
a computer virus-free network, the sender does not warrant that this
transmission is virus-free and will not be liable for any damages resulting
from any virus transmitted.
|