| Re: [mdt-papyrus.dev] Papyrus Developer Builds |
|
Hi, Ø
I hope the goal is to release them as an official Papyrus feature. They are already released as a feature. We could include them in the composite update site, although some users tend to install everything; I’m not sure how many side effects the developer plug-ins have on Papyrus.
For now they should remain separate, until we’re confident enough about their stability (I think Oomph users already have them so they’re probably “good enough”, but since the tests are not executed in an environment which includes them, I wouldn’t take the
risk yet) Ø
Is there any recommended naming convention for these plugins ?
Since developer builds were not “part of” the Papyrus project initially, they didn’t follow any strong convention. Ø
Is there a reason for some developer plugins not to be in the build ? As I said, I only configured the build. The feature, update site, poms... were already configured; I didn’t change anything (I only updated the dependencies for Mars, since the Mars developer plug-ins were still
built against the Luna update site). So, I’ve no idea what’s actually included and what isn’t. Since these developer plug-ins have been barely used so far, I would encourage all developers to install them and report (and fix :) ) any issue. In a few months, if we’re satisfied with them, we can consider
promoting them (e.g. including them in the global Papyrus update sites, along with Main & Extra) Note: if you already installed some of the developer plug-ins via “Export plugins...”, you may need to uninstall them before installing the developer feature, to ensure clean update scenarios. Regards, De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de MAGGI Benoit 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 |