Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Code compilation error - lost many things

Title: Raphaël FAUDOU
Yes, it compiles but we lost many things :
  • all the work about dead code (unused tags) => 1 week effort from thomas lost
  • dirty mode fixed by Thomas does not work anymore => 4 days effort lost and not usable
  • several NPE exceptions that had been managed (additionnal tests to avoid them) => removed => 1 week most
  • Thomas name has disappeard from headers => completely innaceptable
We have the feeling to have come one month back and it is a very disappointing situation :-(
We are blocked for our work on the SysML profile support and for BDD and IBD diagrams.

This is a red signal as we can not continue working like that (frustration, much time consumed).

As immediate actions, I request that :
1/ the backbone code be reverted from two days ago.
2/ control mode fixed as it is a blocking point for collaborative work
3/ backbone evolutions done by Cedric be commited on a branch and not on the head

Thanks
raphaËl





Cedric Dumoulin a écrit :

 Hi,

 The head compils and runs again, except the controlMode plugin and the dirtyFlag behavior.
 I will check that asap (tomorrow) and try to find a solution.

 Cedric

Cedric Dumoulin wrote:

 Hi all,

 Please do not commit on the core, especially on backbone, has I am currently trying to recover it .

 Cedric

Thibault LANDRE wrote:
Hi all,

A commit made yesterday (r734) breaks the compilation of the project.

The class NavigatorUtils needs some methods from the class EditorUtils that have disappeared.
It seems that the commit made yesterday was made from a code that wasn't updated.

If you want to work with code from a specific revision, please create a branch.

Another point, before comiting, please ensure that you are up to date with the code on the repository.

Finally, I think it is safier that every developer, specifically on the backbone, get all the source code of the project in their workspace to check if their modifications don't impact other parts of the project.

Regards,

Thibault
_______________________________________________
mdt-papyrus.dev mailing list
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

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev



--

Image Signature IOC Raphaël FAUDOU
Responsable cellule Innovation / bureau méthodes
Head of Innovation & Method Definition
Embedded systems & critical systems
Atos Origin

Tel     : +33 (0)5 34 36 32 89
Tel     : +33 (0)6 10 53 50 44
Mail   : raphael.faudou@xxxxxxxxxxxxxx
Atos Origin
6, Impasse Alice Guy
BP 43045
31024 Toulouse Cedex 3, France

P Avant d'imprimer cet e-mail, pensez à l'environnement. 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.
P Please consider your environmental responsibility before printing this e-mail. 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.


Back to the top