Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Gendoc/developerResources/PropertiesExample"
(→Presentation) |
(→Tag Handler) |
||
Line 23: | Line 23: | ||
==== Tag Handler ==== | ==== Tag Handler ==== | ||
− | * Fill the extension : org.eclipse.gendoc.tags to create new tag | + | * Fill the extension : '''org.eclipse.gendoc.tags''' to create new tag |
− | ** | + | ** the tag contains one attribute : "path" which is required and typed '''java.lang.String''' |
Revision as of 11:25, 26 July 2016
Presentation
The goal of the example is creating a tag named "Properties" which allows the registration of parameters using properties file. The properties file will be referenced through an attribute named "path". This attribute would be able to contain reference to gendoc variables (${project_loc}, ${input_directory}....)
Contributing
Open a bug
first step is to create a new Bug categorized as an enhancement. In our example the created bug is : https://bugs.eclipse.org/bugs/show_bug.cgi?id=484129
Code
The code source of this example can be visible through these 2 gerrit contributions :
General Idea
The good way to create a tag in gendoc is :
- create a handler (implements org.eclipse.gendoc.tags.ITagHandler) which analyze the tag
- create a service (extends org.eclipse.gendoc.services.AbstractService or implements org.eclipse.gendoc.services.IService) which will do business work
It is a common practice in gendoc to separate handlers and services
- Services can be overridden by developers so initial behavior can be changed
- It forces the developer to separate tha analysis of the tag and the business code
Tag Handler
- Fill the extension : org.eclipse.gendoc.tags to create new tag
- the tag contains one attribute : "path" which is required and typed java.lang.String