Eric,
We support the strategy of building a JDT LS client, potentially replacing the Java editor of JDT UI as it would help reducing duplication between Eclipse and a web IDE (eg., Theia).
Given the new strategy, would it make sense to combine JDT, JDT LS and the new client into a single repository (mono-repo) to allow better refactoring across the stack? One of the problems I face internally is getting new engineers onboarded onto the OSS stack. There are too many interdependent Git repositories, which makes setting up a development environment quite challenging. Lots of time is spend in figuring out workflows and setup issues instead of learning the code base and become productive. It gets especially problematic if we need to submit PRs to multiple repositories, waiting for merges, loosing lot of momentum. Working in a single repo would make things *a lot* easier.
It's ok for the people like myself with lots of Eclipse experience. However, I'm bootstrapping a small IDE team, which is not very experienced in working in OSS, different processes and across multiple Git repositories and "sub" projects.
Any idea how difficult it would be to get JDT + JDT-LS into a single repo first and then look at bringing the
prototype into that repo as well?