Hi Javi,
Thanks for the good pointers to get the missing information. It will
help us regenerating the sequence diagram for Papyrus in Eclipse 3.5
environment.
However, according to me, there is one issue working that way with
several plug-ins required for MDT Papyrus that we have to retrieve from
Moskitt sources repositories.
As MDT papyrus and Moskitt have not the same life cycle and not exactly
the same goals, what comes from Moskitt is contribution and not part of
the MDT Papyrus development.
This was helpfull to start the project, as were the TOPCASED and OBEO
contributions to get a large code base for first commits.
But now the MDT papyrus source code evolves in synchronization with the
Eclipse train (Galileo release), with a given roadmap and with
strategic goals like OMG UML conformance and with a certain level of
quality (somthing like the TOPCASED quality toolkit). We can accept
contributions (and we are very happy about that) but we have now to
apply the process of analysing those contributions : is the code
technically compatible to our Eclipse version reference (Galileo)?
compatible with the MDT Papyrus foundations (backbone)? to the code
formatting we want (checkstyle configuration)? to the UML conformance
level we want to reach (more than 90%)?
This analysis might take long time if we have no information about
those contributions and in some cases it can lead to the decision of
not accepting the contribution for the current release.
As a conclusion, I think that we need to clarify the organization in
terms of involvment: could you please precise if you want to continue
participating in an integrated way to the MDT papyrus (meaning that you
share MDT papyrus goals, roadmap and follow the conference calls) or do
you prefer limiting your efforts to a contributor role?
Thanks for your clarification
best regards
raphaël
Francisco Javier Cano a écrit :
Hi,
regarding the problems you can fins when opening the gmfgen models
from MOSKitt:
those .gmfgen models are extended with two gmfgen extensions we use
in MOSKitt.
Here you can find two plugins that hace the models and source of
those gmfgen extensions.
http://subversion.moskitt.org/gvcase-mdt/trunk/es.cv.gvcase.mdt.common.gmfextension.appearance/
http://subversion.moskitt.org/gvcase-mdt/trunk/es.cv.gvcase.mdt.common.gmfextension.mutating/
Those URLs point to the sources of two MOSKitt plugins that have the
required extensions to open the extended .gmfgen models.
Those plugins have to be downloaded to an Eclipse workspace and then
exported as deployable plugins.
The resulting plugins have to be then added to the working Eclipse
(via an extension location or other mean).
With those plugins loaded in the main instance of Eclipse there
should not be any problem in working with the extended .gmfgen models.
If I remember correctly, Patrick did a good job some time ago by
grouping the MOSKitt .gmfgen extensions inside the Papyrus .gmfgen
extensions.
Ideally, the sequence, activity and statemachine gmfgen models should
work with the Papyrus gmfgen extensions.
Until that happens, using the MOSKitt gmfgen extensions can be used
as described above.
If you have further questions, don't hesitate to ask.
Javi
--
----
Francisco Javier Cano Muñoz
Programador senior
Prodevelop
www.prodevelop.es
-----Original Message-----
From: Thibault LANDRE [mailto:thibault.landre@xxxxxxxxxxxxxx]
Sent: Fri 6/19/2009 14:47
To: Francisco Javier Cano
Cc: FAUDOU Raphael; PERICO Emilien
Subject: [Papyrus] Moskitt GMFGen
Hi Francisco Javier,
I saw that you commited the gmfgen used for the sequence and activity
diagram. But we can't open them because they required the class
"MutatingCanvas" and the Package
"http://es.cv.gvcase.mdt.common.gmfgenextension.mutating"
Where can we find these missing elements in order to open the gmfgen ?
Cheers,
Thibault
--
Raphaël FAUDOU
 |
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. |
|
