eclipse-xtext / eclipse-xtext/xtext
m2e: Wrong name of created Preference Store derived from StandaloneSetup
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
If someone overrides the StandaloneSetup for his language e.g.
PlatformServiceStandaloneSetup extends ServiceStandaloneSetup,
the name of the PreferenceStore containing the outputconfiguration settings is derived from the
standalone setup name, here packagename.PlatformService,
but IPreferenceStoreAcess expects the name of the language.
Therefore the settings are not found in the EclipseOutputConfigurationProvider.
As a workaround someone could override the qualifier of the PreferenceStoreAcessimpl, right?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace how StandaloneSetup-derived names reach the PreferenceStore and how IPreferenceStoreAcess is used by EclipseOutputConfigurationProvider. Compare the PlatformServiceStandaloneSetup and ServiceStandaloneSetup example described in the issue, then verify that output configuration settings are found under the language name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100