Thanks, Cedric,
I have raised bug 489206 [1] for moving the uml.diagram.emftree project into the examples.
As for the service registry projects, they will always remain in the repository history. If and when there is a plan to integrate these into Papyrus in some way, they can easily be retrieved from the Mars branch, any tag that includes them, or even from the history of the master branch if necessary. But there seems to be no such plan, and the Papyrus team has decided to use feature branches instead of sandboxes and other staging directory type of structures for off-line work, so I don’t think it would be appropriate just to move them somewhere else.
Cheers,
Christian
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=489206
On 8 March, 2016 at 07:19:09, Cedric Dumoulin (cedric.dumoulin@xxxxxxxxxxxxxx) wrote:
Hi,
Yes, emftreeis an example of EMF Editor into Papyrus. Its
place is certainly in the examples. It can also be used to explore
Papyrus emf models.
For the serviceregistry.* projects (Here also I am the
author), maybe we can move it in a spare place, rather than
deleting it. It still can be used.
Cedric
GERARD Sebastien 166342 a écrit :
It is an example of an EMF editor into Papyrus. So
let’s move it in examples.
I guess it is Cedric that is the author of this
plug-in.
Hi Christian,
Unfortunately no, there is still at least this
project:
Ø
plugins\uml\diagram\org.eclipse.papyrus.uml.diagram.emftree
I’m not aware of what is the usage of this plugin, but
Camille suggested to move it to example.
Are you aware of its usage?
Regards,
Benoit
Hi, Team,
The following projects that are no longer used by Papyrus,
or that never were, are deleted from the master branch of the git
repo:
·
plugins/developer/org.eclipse.papyrus.doc
[1]
·
plugins/developer/org.eclipse.papyrus.infra.extendedtypes.elementtypeview
[1]
·
plugins/infra/core/serviceregistry/org.eclipse.papyrus.infra.core.serviceregistry
[2]
·
plugins/infra/core/serviceregistry/org.eclipse.papyrus.infra.core.serviceregistry.edit(or)
[2]
·
plugins/infra/core/serviceregistry/org.eclipse.papyrus.infra.core.serviceregistry.tests
[2]
You probably didn’t have these in your workspace but, if
you did, when next you pull, Eclipse will understand that they are
deleted and will just close them for you.
With
this and the addition of a few bundles to shipping features that
had previously been omitted, I think that now all of the
projects in the plugins/ tree in
git are supported, maintained, included in the builds, and shipped
in the Papyrus Main or Developer Tools distribution.
See the
referenced bugs for further information.
Cheers,
Christian
[1]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=488559
[2]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=488558
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
|
