| [mdt-papyrus.dev] Papyrus components: creation of a dedicated project to hold shared elements? |
Dear all, As you probably know with Benoit, we have tried to split/externalize some Papyrus features outside the main Papyrus git repository. It is the case for SysML [1], RobotML [2], Moka or Designer [3]. The management of these projects highlights some difficulties in term of homogeneity. Other projects are now following also the same guidelines (Productline) We would like to propose to externalize some shared elements of Papyrus components inside a dedicated git repository. The proposition could be the following: · Creation of a git repository papyrus-components · With a gerrit and a set of job · This repository will hold o Share documentation across the Papyrus components § Conventions § Rules § Developer elements o Shared Standard Operating Procedures, § Hudson job creation and management (template to duplicate for future components) § such as the release process o Creation of a parent pom that will hold the major configuration for Tycho o Creation of a shared publish script in order to ensure the homogenization of the release process o Creation of a shared target platform based upon the different Papyrus release · Release of this elements through o A p2 o And the official eclipse nexus repository · All Papyrus components will have as parent pom this papyrus-components pom o This will ensure at least a share Tycho configuration o Etc… I would appreciate your comments (pro and con) and how to improve this proposition to reach a better continuous integration system among the Papyrus components galaxy. Francois [1]: https://www.eclipse.org/papyrus/components/sysml/ [2]: https://www.eclipse.org/papyrus/components/robotml/ [3]: https://www.eclipse.org/papyrus/components/designer/
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
