[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: Compilation errors, was [[mdt-papyrus.dev] Code Movement, ipzilladone, planning]
|
This discussion has already been done 6 months ago (Horizontal Layer and vertical layer...). No need to argue more. For existing dependencies, this is just an historical issue, with several plugins coming from old projects. This should be fixed fast. There should be of course no dependency from core feature to exterior (by definition).
Here is an extract from the MDT Papyrus proposal (discussion from may 2008) (http://wiki.eclipse.org/Talk:MDT-Papyrus-Proposal)
Papyrus Proposed Architecture
[Cedric] I will try to clarify the actual proposed architecture.
* First of all, the idea is to have "plug and play" diagrams: to add a diagram, you add its plugin, and, thanks to the eclipse extension mechanism, the diagram should be accessible in Papyrus Editor.
* Papyrus Editor should support GEF diagrams, GMF generated diagrams, actual UML2 Tool diagrams (MDT), EMF trees or any home made diagrams. It is not dedicated to GMF, nor a GMF demonstrator.
* The Papyrus Backbone provide the infrastructure to support multidiagrams accepting any kind of diagrams. The backbone should be independant from any diagrams technologies.
* Various diagram types can be organized by their technologies: GEF, GMF, UML2Tool... For each technology, we could provide the basic support for this technology. This is done actually in (org.eclipse.papyrus.scribe.core, org.eclipse.papyrus.uml2tools, org.eclipse.papyrus.gmf)
Remi
---------------------------------------
Rémi SCHNEKENBURGER
CEA LIST (Saclay)
91191 Gif/Yvette Cedex
---------------------------------------
UML2 modeler: www.papyrusuml.org
-----Message d'origine-----
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Jerome BENOIS
Envoyé : mercredi 26 novembre 2008 14:41
À : Papyrus Project list
Objet : Re: Compilation errors, was [[mdt-papyrus.dev] Code Movement,ipzilladone, planning]
+1 for an independant core
+1 for the lifecycle management propose by Raphael.
Jérôme.
Le mercredi 26 novembre 2008 à 14:31 +0100, Raphael FAUDOU a écrit :
> +1 for independant core
> More generally I see two axes : the backbone as an horizontal layer,
> with a dedicated lifecycle and languages like UML as vertical
> components plugged on the backbone but leaving in different
> lifecycles.
> regards
> raphaël
>
> MRAIDHA Chokri 176997 a écrit :
> > +1 for an independent core.
> >
> >
> >
> > Until end of December I am planning to initiate the profile
> > management for Papyrus.
> >
> >
> >
> >
> >
> > Chokri
> >
> >
> >
> >
> >
> >
> >
> >
> > ____________________________________________________________________
> > De :mdt-papyrus.dev-bounces@xxxxxxxxxxx
> > [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Cedric
> > Dumoulin
> > Envoyé : mardi 25 novembre 2008 22:50
> > À : Papyrus Project list
> > Objet : Compilation errors, was [[mdt-papyrus.dev] Code Movement,
> > ipzilladone, planning]
> >
> >
> >
> >
> >
> > Hi,
> >
> > Thanks Patrick and Remy for the refactoring.
> > I have checkout the entire new structure. Checkout is ok.
> > Then, I have tried to import only the projects contained in the
> > core, and got some compilation errors in the project
> > core/org.eclipse.papyrus.tabbedproperties.core/
> > This project requires other projects located in uml :-(.
> > I think we should have a core independent from projects located
> > elsewhere. Does other commiters agree with that ?
> >
> > Cedric
> >
> > TESSIER Patrick 202707 wrote:
> >
> > Hi,
> >
> > I have finished the movement of the code and we have done the
> > ipzilla
> >
> >
> >
> > The code is now at:
> >
> > https://speedy.supelec.fr/Papyrus/svn/Papyrus/eclipse/core/
> >
> > https://speedy.supelec.fr/Papyrus/svn/Papyrus/eclipse/other/
> >
> > https://speedy.supelec.fr/Papyrus/svn/Papyrus/eclipse/scribe/
> >
> > https://speedy.supelec.fr/Papyrus/svn/Papyrus/eclipse/uml/
> >
> >
> >
> > the revision of the code done for the ipzilla is 2749.
> >
> >
> >
> > Each partner can write what it will until end of december?
> >
> >
> >
> > Plan to do on Papyrus until december:
> >
> > - Patrick Tessier: I will finish the class diagram and work on
> > the outline.
> >
> > - Cedric Dumoulin:
> >
> > - Thibault Landre:
> >
> > - Emilien Perico:
> >
> > - Jérôme Benois:
> >
> > - Francisco Javier Cano Muñoz:
> >
> > - David Servat:
> >
> > - Remi Schnekenburger:
> >
> > - Chokri Mraidha:
> >
> > - Jacques Lescot
> >
> >
> >
> >
> > ---------------------------------------------------------
> >
> > Patrick Tessier
> >
> > Research Engineer
> >
> > DRT LIST/DTSI/SOL/LISE CEA-Saclay
> >
> > 91191 Gif sur Yvette Cedex
> >
> > Tel: 01 69 08 48 63
> >
> > www.papyrusuml.org
> >
> > ---------------------------------------------------------
> >
> >
> >
> >
> >
> >
> >
> > ____________________________________________________________________
> > De : mdt-papyrus.dev-bounces@xxxxxxxxxxx
> > [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de TESSIER
> > Patrick 202707
> > Envoyé : mardi 25 novembre 2008 13:00
> > À : Papyrus Project list
> > Objet : [mdt-papyrus.dev] Movement of the code
> >
> > Hi,
> >
> >
> > We will move the code of payrus in new directory on the svn, as we
> > have decided at the last precommitting meeting.
> >
> >
> >
> >
> >
> > I will send an email with directories path as soon as I have
> > finished.
> >
> >
> >
> >
> >
> > Patrick
> >
> >
> >
> >
> >
> > ---------------------------------------------------------
> >
> > Patrick Tessier
> >
> > Research Engineer
> >
> > DRT LIST/DTSI/SOL/LISE CEA-Saclay
> >
> > 91191 Gif sur Yvette Cedex
> >
> > Tel: 01 69 08 48 63
> >
> > www.papyrusuml.org
> >
> > ---------------------------------------------------------
> >
> >
> >
> >
> > _______________________________________________
> > 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
> Atos Origin Midi Pyrénnées
>
> Tel : +33 (0)5 61 39 75 35
> Tel : +33 (0)6 10 53 50 44
> Mail :
> raphael.faudou@xxxxxxxxxxxxxx
> Immeuble AEROPOLE 4 5 avenue Albert
> DURAND - 31700 BLAGNAC
>
>
> 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.
>
>
> _______________________________________________
> 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
- References:
- [mdt-papyrus.dev] Movement of the code
- From: TESSIER Patrick 202707
- [mdt-papyrus.dev] Code Movement, ipzilla done, planning
- From: TESSIER Patrick 202707
- Compilation errors, was [[mdt-papyrus.dev] Code Movement, ipzilla done, planning]
- RE: Compilation errors, was [[mdt-papyrus.dev] Code Movement, ipzilladone, planning]
- From: MRAIDHA Chokri 176997
- Re: Compilation errors, was [[mdt-papyrus.dev] Code Movement, ipzilladone, planning]
- Re: Compilation errors, was [[mdt-papyrus.dev] Code Movement, ipzilladone, planning]
- Prev by Date:
Re: Compilation errors, was [[mdt-papyrus.dev] Code Movement, ipzilladone, planning]
- Next by Date:
Re: [mdt-papyrus.dev] Code Movement, ipzilla done, planning
- Previous by thread:
Re: Compilation errors, was [[mdt-papyrus.dev] Code Movement, ipzilladone, planning]
- Next by thread:
Re: [mdt-papyrus.dev] Code Movement, ipzilla done, planning
- Index(es):