Papyrus/Papyrus Developer Guide
- 1 Development Environment
- 2 Getting the code
- 3 Papyrus Architecture
- 4 Contributing to Papyrus
- 5 How To ...
- 6 Release Engineering
To ease the development on Papyrus, each member of the team works with basically the same configuration. There are two ways to get yrou development environement:
- downloading and installing Eclipse
- using the Eclipse Installer (by Oomph) to manage your Papyrus development workbench.
You can download a fresh Eclipse Package release on this page. We advice you to download the Eclipse Committer version.
Papyrus Oomph Setup Model
The Eclipse Installer provides a set-up model for Papyrus, making it easier than ever to get a complete Eclipse workbench up and running for development on the Papyrus source code. Just download the Oomph Installer from the linked wiki page and follow the simple wizard to create your IDE and import the Papyrus source projects that you want to work on.
Pick any product you like on the first page, but be sure it's the latest release of that product for the Papyrus stream you're working on. For example, if you're working on the Luna service stream of Papyrus, you need the Luna release of Eclipse. On the second page, expand Eclipse.org / Papyrus to see the various components that you can import to work on. Pick any combination of the leaf-level sub-(sub-)projects, even all of them if you like. In the third page where you specify variables such as install location, workspace location, git clone, etc. be sure to choose "Luna" for the Target Platform. This ensures that you will be set up to work on Papyrus Luna (SR1), which is the only development stream currently supported by the setup model (until Mars development gets under way).
Contributing your changes is easy because Oomph will clone the Papyrus Git repository for you and configure Gerrit push.
Amongst possibly other details, the setup model configures:
- your IDE with all of the tools needed to edit and build the source projects you choose
- your workspace with a Git clone and the source projects imported from it that you choose
- a PDE target that includes all of the dependencies required by Papyrus plus the latest nightly build of Papyrus, itself, so that you can import only a subset of the (many) source projects but still run the complete Papyrus toolset in a run-time workbench
- Mylyn queries for current open bugs and enhancements in the Papyrus bugzilla database
- Mylyn queries for the status of the latest Papyrus automated builds, including tests
- Mylyn queries for open Gerrit reviews
- preferences enforcing the Papyrus standard compiler and code formatter/template settings
Please raise bugs if you see any problems in the setup configuration.
Follow the following link for a step by step installation guide: Oomph setup guide
Following is a description of the basic configuration:
- The latest Eclipse release pertinent to your usecases (Modeling, Committer, java, etc)
- the Papyrus release (matching your Eclipse version), installed from the relevant Papyrus update site
- Papyrus SDK
- Papyrus Toolsmiths
- Papyrus Releng Tools
- Papyrus User Examples
Additional useful tools
- install the source version of the Papyrus dependencies (EMF, GMF, MWE2, XTEND, XTEXT, UML2, UML2 Extender SDK) (relevant to your usecases)
OpenJDK 1.8 (or higher) is recommanded.
Getting the code
If you are not using Oomph to set your environment you will need to fetch the code manually.
Cloning the Git repository and importing the code
The Papyrus code and some documents are located in a Git repository. In the website http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git you will find the most recent activity information of the repository and, at the bottom of the page, you will find the URIs of the Git repository (e.g., http://git.eclipse.org/gitroot/papyrus/org.eclipse.papyrus.git).
Follow this quick tutorial if you never used Git before and want to know how to import the source files of one or more Papyrus plugins in your Eclipse workspace.
Papyrus Plugin Naming Scheme and Folders Structure
- Papyrus plugins naming scheme and folder structure used to locate and name plugins is described here: Papyrus/Papyrus_Developer_Guide/Papyrus_Plugin_Naming_Scheme
Contributing to Papyrus
Each developer must follow the following rule in addition to the aforementioned Developer Charter.
- Configure the header template according to your company: Eclipse Preferences -> Java -> JAutodoc
- Configure your Eclipse.ini file adding this line in the vmargs:
-Duser.name=FirstName LastName (Company) <user@email>
- Java 1.8:
- Eclipse Preferences -> Java -> Compiler
- Eclipse Preferences -> Java -> Installed JREs
- VM Arguments for debug mode:
-Dosgi.requiredJavaVersion=1.8 -Xms768m -Xmx1024m -XX:+CMSClassUnloadingEnabled
Version Management Tooling
There are two way to manage your code version:
- define yourself the API baseline for Papyrus using Eclipse Preference API Baseline
- Oomph includes a way to manage the version changes between two releases as illustrated here
Retrieve configuration files
The note explains how to install the templates in your environment.
- the goal of the externalization process is to distinguish the string used as messages and visible by the final user and the string required in your code, but not visible for the user,
Follow this link for a guide on externalization in Eclipse.
Papyrus Plug-ins and Features
New plugin should follow the submition process describe here: Papyrus New Plugin Submission Process
Write Documentation for Papyrus
How to - Related to documentation Papyrus Developer Guide/Writing Documentation
Code Contributions and Reviews
How To ...
Papyrus Diagram Generation
- Papyrus generation mechanism is explained here: Papyrus Developer Guide/Papyrus diagram generation
Model your papyrus development, and generate User doc
- How To - create your model (requirements, use cases, design, tests) ... Papyrus Developer Guide/Model your development
Papyrus Code Examples
- How to - Related to Papyrus code,Papyrus Developer Guide/How To Code Examples
Rcptt is under evaluation but a developer guide can be find here.
The specifications are available here:
Future Release plans should become available here:
Contributing to the plan for the release
- Papyrus API Evolution Reports: Papyrus Developer Guide/API Evolution Reports
- Papyrus Hipp standard guide: Papyrus Developer Guide/How to use the Hipp and its functionalities.