Skip to main content
Jump to: navigation, search

Papyrus/Code Standards

< Papyrus
Revision as of 10:37, 19 November 2020 by (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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 and Plugins

We prefer when the Bundle-Name and Bundle-Vendor fields are externalized in the properties file. So we expect a file (or sometimes renamed into for Plug-In, and a file for Feature. A such file must be embedded in the binary build, so you must check in the Build Configuration tab that the file is selected.


  • ID:
    • Main Papyrus components: org.eclipse.papyrus.<>.feature
      • e.g. org.eclipse.papyrus.infra.core.feature
  • Name: Papyrus <Feature Name>
  • Each feature.xml file must contains:

Copyright (c) 20XX CEA LIST
All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License 2.0
which accompanies this distribution, and is available at
SPDX-License-Identifier: EPL-2.0

    • in Information Tab -> License Agreement
      • Check the field Shared License,
      • License Feature ID: org.eclipse.license,
      • License Feature Version: 2.0.2.
  • The file must contain the following files in the "Binary build" section:
    • (When available)
    • feature.xml

Additional information for the build process

The build process also needs to know where is the license. There are 2 solutions :

Option 1

In the main pom.xml file (often in the pom.xml of releng/folder), you must write:


Option 2

Your target platform definition file (tpd) must also contains:

location "" eclipse-license { lazy

Back to the top