OpenLiberty / OpenLiberty/liberty-tools-eclipse
Consider associating all *.xml files with Generic Text Editor, not just server.xml
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 16
- Forks
- 20
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 16
Description
We might have to ask the WWD list why this doesn't already seem to happen, given the org.eclipse.wildwebdeveloper.xml plugin already does:
<extension
point="org.eclipse.ui.editors">
<editorContentTypeBinding
contentTypeId="org.eclipse.core.runtime.xml"
editorId="org.eclipse.ui.genericeditor.GenericEditor">
</editorContentTypeBinding>
</extension>
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
Start with the org.eclipse.wildwebdeveloper.xml plugin and its org.eclipse.ui.editors content-type binding for org.eclipse.ui.genericeditor.GenericEditor. Investigate why the binding does not cover all *.xml files, using the linked WWD mailing list if needed. Done means XML files are associated with the Generic Text Editor rather than only server.xml.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100