text: Papyrus Plugin Naming Scheme
  This page explains:
  - how Papyrus plugins are named and located.
  - the structure of the trunk and branches
  All papyrus plugin should start with the same prefix:
  org.eclipse.papyrus
  Contents
  Naming Scheme
  So you want to propose a new plugin. You need to give it a name.
  All papyrus plugins should start with the same prefix:
  org.eclipse.papyrus
  But this is not enough. The next step is to decide where your plugin should be located:
  - Read carrefully the next paragraph, and decide in which folder/subfolder your plugin will be located
  - Use the proposed prefix (ex: org.eclipse.papyrus.example. )
  - If you want to contribute a set of plugins, give them a namespace name to identify all of them
  - Try to give a self explanatory name.
  Folders Structure
  The trunk and the branches have the same structure. Here we will only describe the trunk structure.
  The trunk contains the following folders:
  - plugins - contains all plugins included in the Papyrus distribution: core, main uml diagras, sysml
  - tests - contains tests plugin. The internal structure is the same as plugins, but here we have tests.
  - extraplugins - contains plugins that can be added to Papyrus in order to bring some extra functionalities: java reverse, autolayout, marte, ...
  - incoming - this is a special folder used by Papyrus developper to propose new plugins (see Papyrus_New_Plugin_Submition_Process)
  - examples - contains some example of plugins, for user and developper.
  - sandbox - contains new projects which the development is not yet finished and copies of existing projects for large changes (Refactoring, new features, ...)
  These folders can also contains subfolders.
  plugins
  This folder contains sub folders. All plugins in the sub folders form the main Papyrus distribution.
  tests
  This folders contains subfolders, each one dedicated to a kind of test:
  - junit
  - recipes
  - swbot
  Each subfolder mimic the same structure as the trunk. The names of the plugins are usually the same name as the tested plugin, suffixed with the type of test.
  extraplugins
  This folder contains plugins that can be added to Papyrus in order to bring some extra functionalities.
  incoming
  This is a special folder used by Papyrus developper to propose new plugins (see Papyrus_New_Plugin_Submition_Process)
  examples
  There is two kind of examples:
  - user examples
  - Papyrus developer or customizer examples
  The folder contains subfolders for each kind of examples.
  Actual Sub-Folders and Proposed Refactoring
  The following table try to resume the actual existing folders, their purpose, and eventually the proposed refactoring: