eclipse-xtext / eclipse-xtext/xtext
Deal with Template deprecation/new superclasses at eclipse
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
eclipse decided to introduce new supetypes, let the old type inherit from them, and deprecate the old ones
this is not sovable on Xtext side without
- breaking mimal eclipse version (currently oxygen)
- breaking api by changing super types and method parameters.
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 by reviewing the Eclipse deprecation and new-supertype changes described in the issue, then identify the Xtext APIs affected by changing supertypes and method parameters. Done requires an explicit decision on whether to break the minimum Eclipse version, break the API, or leave the compatibility issue unresolved; no files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100