Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Papyrus/Code Standards
< Papyrus
Revision as of 10:37, 17 September 2020 by Pauline.deville.cea.fr (Talk | contribs) (→Java classes)
Coding rules for Papyrus plug-ins and features
These rules apply to all plug-ins and features developed for the Papyrus Eclipse project, and distributed under the EPL licence.
Features
- ID:
- Main Papyrus components: org.eclipse.papyrus.<feature.name>.feature
- e.g. org.eclipse.papyrus.infra.core.feature
- Extra components: org.eclipse.papyrus.extra.<feature.name>.feature
- e.g. org.eclipse.papyrus.extra.marte.feature
- Main Papyrus components: org.eclipse.papyrus.<feature.name>.feature
- Name: Papyrus <Feature Name> (Incubation)
- e.g. Papyrus core (Incubation)
- e.g. Papyrus Marte (Incubation)
- Each feature must contain the files epl-v10.html and license.html (April 9, 2014)
- The build.properties file must contain the following files in the "Binary build" section:
- epl-v10.html
- feature.properties (When available)
- feature.xml
- licence.html
- The build.properties file must contain the following files in the "Source build" section:
- build.properties (Optional)
- epl-v10.html
- licence.html
