Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Papyrus and Helios 
Hi all,
I see the trouble, We'll see what we can do to join the Helios release train. 

I will give you more information in the next days.

Regards,

--
Goulwen Le Fur - goulwen.lefur@xxxxxxx

TANGUY Yann 176637 a écrit :
My understanding is that we basically cannot be part of Helios if we rely on a non Helios component…
What would it mean to have Papyrus integrated to Helios release if it does not work (I mean unless an additionnal non-helios install ?). 


I could not figure out other components in same situation.


------------------------------------------------------------------------
*De :* mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] *De la part de* GERARD Sebastien 166342 
*Envoyé :* jeudi 26 novembre 2009 08:58
*À :* Papyrus Project list
*Objet :* RE: [mdt-papyrus.dev] Papyrus and Helios


Dear all Papyrus,
About the answer sent on the plan of EEF w.r.t. Helios: they will not commit to follow the Helios train, however they said that they will follow the process. 


My question is: do we think it may be a risk for us? If yes, why?


Thanks for your comments.


Sébastien.


------------------------------------------------------------------------
*De :* mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] *De la part de* TANGUY Yann 176637 
*Envoyé :* mardi 24 novembre 2009 16:02
*À :* Papyrus Project list
*Cc :* TANGUY Yann 176637
*Objet :* RE: [mdt-papyrus.dev] Papyrus and Helios


What is the plan regarding the Helios version of GMF,
do we have to migrate Papyrus specific template, code generation and gmfgen extension for M4 (+3) ? 


------------------------------------------------------------------------
*De :* mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] *De la part de* Kenn Hussey 
*Envoyé :* vendredi 20 novembre 2009 15:03
*À :* thibault.landre@xxxxxxxxxxxxxx; Papyrus Project list
*Objet :* Re: [mdt-papyrus.dev] Papyrus and Helios
I think it's safe to assume that the deadline is M4 (December 16 for Papyrus, as a +3 project), even if it isn't explicitly stated. 


Cheers,


Kenn
2009/11/20 Thibault LANDRE <thibault.landre@xxxxxxxxxxxxxx <mailto:thibault.landre@xxxxxxxxxxxxxx>> 

Hi Sebastien,
I don't know about the deadline for migrating to Helios. It might be an implicit requirement before M4.
For all actions that need to be done before M4, please refer to the mail called "Re: [mdt-papyrus.dev] Papyrus and Helios Release Train" that I sent on this ML on November 6th 

Regards,

Thibault



GERARD Sebastien 166342 a écrit :

    What is the deadline for migrating?
------------------------------------------------------------------------ 

    *De :* mdt-papyrus.dev-bounces@xxxxxxxxxxx
    <mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx>
    [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx
    <mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx>] *De la part de*
    Emilien PERICO
    *Envoyé :* jeudi 19 novembre 2009 10:51
    *À :* Papyrus Project list
    *Objet :* Re: [mdt-papyrus.dev] Papyrus and Helios
Hi Sébastien, 

    Good news. It implies that we should migrate to Helios platform as
    soon as possible for our development.
    We have to take care of this task, I think the earlier we'll upgrade
    papyrus to helios, the better

    GERARD Sebastien 166342 a écrit :

    Dear Payrusers,
At CEA, we have checked it was ok to use helios in the project we 
    are involved, and the conclusion is ok. According to that, CEA is ok
    for Papyrus joiing the Helios Train. So I think it is ok for Papyrus
    joining the Helios train.
One consequence is that builds of Papyrus will be public in M4 so 
    very soon…
Sébastien.
Dr. Sébastien Gérard 

    Head of MDD for DRES research project

    CEA LIST/LISE

    Boîte courrier 65, GIF SUR YVETTE

    CEDEX, F-91191 France

    Phone/fax : +33 1 69 08 58 24 / 83 95

    Leader of the Eclipse Component Papyrus (The UML2 Graphical
    Modeler): www.papyrusuml.org <http://www.papyrusuml.org>

    http://www.eclipse.org/modeling/mdt/?project=papyrus
Before printing, think about the environment 



    ------------------------------------------------------------------------
_______________________________________________ 

    mdt-papyrus.dev mailing list

    mdt-papyrus.dev@xxxxxxxxxxx <mailto:mdt-papyrus.dev@xxxxxxxxxxx>
    <mailto:mdt-papyrus.dev@xxxxxxxxxxx
    <mailto:mdt-papyrus.dev@xxxxxxxxxxx>>



    https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
-- 
    *Emilien PERICO*
    *Ingénieur - Atos Origin*
    Tel : 05 34 36 34 49

    www.atosorigin.fr <http://www.atosorigin.fr> <http://www.atosorigin.fr>
*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.


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



    _______________________________________________
    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 <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

Back to the top