Description Cedric Dumoulin 2011-04-05 09:10:28 EDT

Some plugins names or locations need a refactoring.
We need to identify such plugins, and take the corresponding actions. This bug serve as a root to identify such plugins, or group of related plugins. 
The following wiki try to summarize Papyrus naming scheme and plugin locations (http://wiki.eclipse.org/Papyrus_Plugin_Naming_Scheme).

For each identified plugin, I propose to open a sub-bug, child of this root bug. Each sub-bug identify clearly:
- the 'old' name and old location
- the 'new' name and 'new' location
- optionally an explanation of the plugin purpose/proposed name

Plugin refactoring should be done with the 'svn move' command, in order to keep track of the previous history.
This bug does not apply to plugins submitted in the 'incoming' folder.

Some common reasons leading to propose refactoring: 
- name is too general
- name doesn't depict the plugin purpose
- plugin location is wrong (uml, sysml, example, core, ...)
- plugin name doesn't contains the targetted 'folder' location (core, uml, sysml, example, ...)
- ...