| Re: [mdt-papyrus.dev] Papyrus Developer Builds |
|
Hi Camille, Thanks for publishing the developer plugin, I think it will help a lot the newcomers on the project. I hope the goal is to release them as an official Papyrus feature. I have some questions to the team :
-
Is there any recommended naming convention for these plugins ?
ð
Most of them are not in org.eclipse.papyrus.developper namespace. -
Is there a reason for some developer plugins not to be in the build ? => for example : org.eclipse.papyrus.infra.extendedtypes.elementtypeview Thanks, Benoit De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de LETAVERNIER Camille Hi all, The developer plug-ins of Papyrus are now built daily: https://hudson.eclipse.org/papyrus/job/Papyrus-Luna-Developer/ https://hudson.eclipse.org/papyrus/job/Papyrus-Master-Developer/ The update sites are currently published as artifacts of these builds: The developer build contains a few Debug views (EditPart Spy, EditPolicy Spy, Figure Spy, CSS Spy...), as well as some of the metamodels/code generators used to produce Papyrus plug-ins (Including GMFGen Extension + Codegen
extensions) Everything already existed; I only configured the Hudson jobs to publish them as an installable component. Camille __________________________ Camille Letavernier +33 (0)1 69 08 00 59 -
camille.letavernier@xxxxxx CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE) Papyrus :
http://www.eclipse.org/papyrus |