Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] [Refactoring] Generation of state machien diagram

Hi Arthur,

 

For the build to be operational, some tests needs to be fixed. Those tests which do not work anymore are related to the backbone which you have modified some time ago to introduce the ability to have an history navigation (I guess). And then, as discusses with Tristan, the stone is in your garden waiting you to fix this issue.

 

Cheers… Sébastien.

 

------------------------------------------------------------------------------------------------------------------------------------------------

Sébasten Gérard

CEA Saclay Nano-INNOV

Institut CARNOT CEA LIST

DILS/Laboratoire d’Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE),

Point Courrier n°174

91 191 Gif sur Yvette CEDEX

 

PapyrusLogo_SmallFormat www.eclipse.org/papyrus

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de DAUSSY Arthur
Envoyé : vendredi 25 novembre 2011 14:58
À : Papyrus Project list
Objet : [mdt-papyrus.dev] [Refactoring] Generation of state machien diagram

 

Hi everyone,

 

 I’m currently working on the state machine diagram. I have to add comments and constraints in it. I have done it on the 0.8.X branch and I’m trying to backport it on the trunk.

 As it was said during meetings, I have encountered problems during the generation of this diagram.

 I have created a patch about modifications on templates (See patch in attachment).

 I would like to have review on those modifications before committing because I am not sure about impacts on Sysml/UML diagrams.

 Moreover I have modified gmfgen in state machine diagram in order to be regenerated in the new trunk architecture.

 Last but not least, I would like to know when the build on the trunk will be reactivated. I would need it to create a platform to test my backports on the trunk.

 

Regards,

 

Arthur Daussy

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.

Back to the top