Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Papyrus/Mars Work Description/Improvments/Default naming support"

(Created page with "'''Context''' The goal is to refactor default naming support in order to allow users/developers to refine a default naming convention to name their ElementType. '''Developme...")
 
m
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
'''Context'''
 
'''Context'''
  
The goal is to refactor default naming support in order to allow users/developers to refine a default naming convention to name their ElementType.
+
The goal is to refactor default naming support in order to allow users/developers to refine a default naming convention to name their ElementTypes.
  
'''Development'''
 
  
The main ticket in bugzilla :  
+
'''Developer advice'''
The branch in charge to care of the development:
+
 
 +
This feature feature is strongly linked to the Element type framework that has replaced the Extended type framework.
 +
The developer should install at least one developer plugin to access to the element type view of any element directly by activating a eclipse view.
 +
 
 +
git/org.eclipse.papyrus/plugins/uml/tools/org.eclipse.papyrus.uml.tools.elementtypesconfigurations
 +
 
 +
'''Development Links'''
 +
 
 +
- The main ticket in bugzilla : https://bugs.eclipse.org/bugs/show_bug.cgi?id=458539
 +
 
 +
- The branch in charge to care of the development: https://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/?h=bugs%2F458539-namingconvention
 +
 
 +
- The hudson build : https://hudson.eclipse.org/papyrus/job/Papyrus-Feature-NamingConvention/

Latest revision as of 03:50, 23 February 2015

Context

The goal is to refactor default naming support in order to allow users/developers to refine a default naming convention to name their ElementTypes.


Developer advice

This feature feature is strongly linked to the Element type framework that has replaced the Extended type framework. The developer should install at least one developer plugin to access to the element type view of any element directly by activating a eclipse view.

git/org.eclipse.papyrus/plugins/uml/tools/org.eclipse.papyrus.uml.tools.elementtypesconfigurations

Development Links

- The main ticket in bugzilla : https://bugs.eclipse.org/bugs/show_bug.cgi?id=458539

- The branch in charge to care of the development: https://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/?h=bugs%2F458539-namingconvention

- The hudson build : https://hudson.eclipse.org/papyrus/job/Papyrus-Feature-NamingConvention/

Back to the top