eclipse-xtext / eclipse-xtext/xtext
Double-check releng tools from the xtext org
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
Some build tasks still rely on production code from github.com/xtext
We should review these usages and try to integrate the necessary bits and pieces in the monorepo.
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 build tasks that rely on production code from github.com/xtext and review which usages still point outside the monorepo. Identify the necessary pieces to integrate and verify that the remaining releng tools no longer depend on those external usages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100