Re: [mdt-papyrus.dev] Modification of generation template

[TANGUY Yann 176637 <Yann.TANGUY@xxxxxx>]

Hi Raphael, hi all,

 

Thank you for this clarification.

 

Best regards,

 

Yann

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de FAUDOU Raphael
Envoyé : mercredi 21 mars 2012 21:41
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Modification of generation template

 

Hi Yann, hi all

 

Comments below.

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de TANGUY Yann 176637
Envoyé : mercredi 21 mars 2012 11:07
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Modification of generation template

 

Hi,

 

I’m a bit surprised to learn that you have decided (on you own? without referring to the project lead?) to modify the diagram generation templates, and to re-generate all the diagrams, on the stable branch.

[FAUDOU Raphael] The previous mail may have been confusing so I give details for you and the community.

One week ago we discovered a critical bug concerning “move” command in Papyrus 0.8.2. When moving a model element from one model resource to another, the diagrams were not physically copie : (Bug 374607). Same conclusion for stereotype application.  It leaded to “strange” situations and unpredictable behavior when models are used in collaborative work with many controlled submodels.

We have investigated and have finally decided to fix the bugs at the most generic level possible to get  homogenous behavior in all diagrams. We have done the fix on one diagram and then have sent the previous mail to warn about need to regenerate all diagrams.

 

Since now 3 weeks, we have been preparing the next TOPCASED release (April 3^rd) and we have informed the other papyrus developers on March 6^th  developer meeting that we needed to control commits done at 0.8 branch to fix several critical bugs at backbone level. All present developers were OK and I took time to inform Rémi and Sebastien by email on March 8^th .  So the Papyrus leader and most developers were aware of heavy work on the branch from our side. I’m sorry if you did not get those information. Probably we need to share those kinds of decisions on Papyrus-dev mailing list. I will personally insist on respecting this rule to avoid that some people are not informed.

 

The 0.8.X branch is supposed to be used for maintenance purpose and such changes (and more generally implementing new features) introduce a risk to degrade the stability of Papyrus.

[FAUDOU Raphael] Agree

I don’t think we can get good result if you introduce new features and bugs while the CEA team is trying to consolidate the branch by fixing bugs.

[FAUDOU Raphael] We do not introduce new features and  only focus on bugs fixes for future use of Papyrus editors in production.  Why mentioning CEA team for consolidating the branch? For me it is a goal shared by all Papyrus developers including both CEA and Atos committers. If you have any doubt on that, you can consult SVN activity: http://dev.eclipse.org/viewcvs/viewvc.cgi/branches/0.8.X/?root=MDT_Papyrus&view=log

 

 

Why don’t you plan and add enhancement on the trunk for next Papyrus release, this is the good place for it.

[FAUDOU Raphael] When we get enhancements they will submitted to the trunk. As said previously all our current activity is about fixing bugs (see bugzilla for details).

Hope confusion is over now

 

Regards

Raphaël

 

Regards,

 

Yann

 

 

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de DAUSSY Arthur
Envoyé : mardi 20 mars 2012 11:42
À : Papyrus Project list
Objet : [mdt-papyrus.dev] Modification of generation template

 

Hi all,

 

 During our current development, we have decided to plug the “move command” (see UMLItemSemanticEditPolicy) into the Service Edit mechanism.

 In order to do this we had to modify the generation template. You will find the difference patch in attachment.

 This change has been committed on the 0.8.X branch. We are going to regenerate the diagrams in order to make this impact all the diagrams.

 If anyone has any objections or suggestions for a new implementation on the trunk, I will modify it otherwise I will commit it soon on the trunk.

 

Regards,

Arthur Daussy Atos Origin Intégration 6 impasse Alice Guy BP 43045 31024 Toulouse Cedex 3 Telephone : +33 (0) 5 34 36 32 90 www.atos.net

 

 

---

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 ne pourra être engagé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 engagé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 group liability cannot be triggered for the message content. Although the sender endeavors 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.