Preserve other builders and natures
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 712
- Forks
- 163
- PR merge metrics
- No merged PRs in 30d
Description
Every time after regenerating eclipse project files (with really multiple sub-projects) I'm forced to add (and configure from the beginning!) all other builders all (sub)projects have got except for Scala and Java ones (at my case they are JavaScript and JSHint natures and builders). You can imagine how annoying every updating is. Please, preserve other builders and natures.
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or entry point is named. Reproduce regeneration with a multi-project Eclipse build containing JavaScript and JSHint builders and natures, then trace the project-file generation path; done means existing builders and natures survive regeneration for every subproject while Scala and Java configuration remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, scala
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100