Bug 552024 - The registrations of the TemplateVariableResolvers locate in different places
Summary: The registrations of the TemplateVariableResolvers locate in different places
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.14   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-11 03:14 EDT by Sheng Chen CLA
Modified: 2023-09-23 11:14 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sheng Chen CLA 2019-10-11 03:14:32 EDT 
Hi team,

I have a question regarding to the TemplateVariableResolver registrations.

I noticed that the registrations of the TemplateVariableResolver are in different places.

Take an example of the resolvers for JavaContextType:

- Some are added in code implementation: https://github.com/eclipse/eclipse.jdt.ui/blob/c25e5a83e3a015ddf6bfbef854ccc96a816cf267/org.eclipse.jdt.ui/core%20extension/org/eclipse/jdt/internal/corext/template/java/AbstractJavaContextType.java#L328-L361

- Some are added in the plugin.xml: https://github.com/eclipse/eclipse.jdt.ui/blob/cf6c42522ee5a5ea21a34fcfdecf3504d4750a04/org.eclipse.jdt.ui/plugin.xml#L5607-L5699

Is there any reason for these two different kinds of registration? Is it possible to centralize the registration, like adding all the resolvers in Java code.

Thanks.
Comment 1 Eclipse Genie CLA 2021-10-01 11:38:10 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-09-23 11:14:11 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.