eclipse-xtext / eclipse-xtext/xtext
JDT Facade project
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
In some parts, we use internal members of JDT or use reflection to perform different method calls according to the version of JDT (see https://github.com/eclipse/xtext/pull/3128 and https://github.com/eclipse/xtext/pull/3124)
Se also
We could confine such code in a separate project, acting as a facade for JDT. At least the code using reflection and internal JDT members is not spread over all our projects.
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 reading the linked pull requests 3128, 3124, and 3206, plus issue #3205, to identify the existing JDT internal-member and reflection usage. Define the scope of a separate JDT facade project and verify that this work would confine those compatibility calls rather than leaving them spread across projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100