eclipse-xtext / eclipse-xtext/xtext
Make sure we use the same custom jdt settings in all projects
Open
Nobody has claimed this yet.
bug
confirmed
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
Make sure we use the same custom jdt settings in all projects. there are some projects that dont have custom settings and thus warning behaviour in jdt is different
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 locating the project-specific custom JDT settings and comparing them across the repository. Identify which projects lack those settings and review how their warning behavior differs. Done means all projects use the same custom JDT configuration and the resulting warning behavior is consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100