Hi Mickael,
I have some questions about the proposal and also current JDT-Javac repo state as of today.
There also were few good questions asked on the [1] where I don't see satisfiable answers yet.
Let first try to understand what actually is proposed, because IMO it is not clearly stated.
1) Currently we have two Github organizations with distinct set of committers:
https://github.com/eclipse-jdt
https://github.com/eclipse-jdtls
They host various repositories related to JDT and clear dependencies (JDT LS uses JDT). One of the repositories under JDT LS is the "JDT-javac" (https://github.com/eclipse-jdtls/eclipse-jdt-core-incubator), used by JDT LS only. So far so good.
If the proposal says "moving JDT-Javac repo as a subproject of JDT in general", does it mean moving JDT-javac repository from https://github.com/eclipse-jdtls to https://github.com/eclipse-jdt or creating a fully independent *third* organization, let name
it https://github.com/eclipse-jdt-javac?
This "This would then be a different subproject, with a different schedule, committers set, GitHub oraganization than "main" JDT" indicates it is supposed to be something like https://github.com/eclipse-jdt-javac?
2) The https://github.com/eclipse-jdtls/eclipse-jdt-core-incubator is currently a *fork* of https://github.com/eclipse-jdt/eclipse.jdt.core repository, with all the code from JDT included, some modified & some added. I can't see how a fork can be an independent
subproject, but probably this can be solved by properly separating the code, pushing all modified JDT code upstream and creating a fully independent set of projects that *consume* JDT core instead of forking it. So in my understanding, before anything new
& independent is created, "forking" problem has to be solved, otherwise it is not independent project per definition.
3) With the two points above, the only possible understanding of this proposal (as of today) is a new "https://github.com/eclipse-jdt-javac" organization which can then do whatever it wants to do, not a fork from any repository under https://github.com/eclipse-jdt
and also not a child repository under https://github.com/eclipse-jdt.
So let assume 3) is given, the proposal is then: "Let create new JDT based (but not forked) Eclipse project which will be run by as a separate github organization with its own committers team, its own repositories and everything else (except code dependencies)
independent from JDT, JDT LS, Eclipse SDK or Simrel".
Such proposal should not affect JDT project (https://github.com/eclipse-jdt) and should improve its relationship to JDT LS project (https://github.com/eclipse-jdtls), because the dependency of JDT LS to JDT-javac would be cleaned up as well as forking
/ using forked JDT code in JDT LS build is stopped.
With that assumptions above (independent organization & no forked JDT code), I don't see how JDT Core can have objections to the proposal.
Everyone can propose and create a new Eclipse project and run it if there are enough energy, resources and interest from the community.
if, however, the proposal is to keep forking JDT repo but create new "independent" Eclipse project based on JDT or move the forked JDT repo under https://github.com/eclipse-jdt organization, then this I would vote against it. Creating new JDT based project
based on fork will divide the community, and that is not benefitial for JDT. Merging current code to JDT repo has also disadvantages as it is not really used/needed by JDT but wil all strong dependencies to latest JDK builds/javac if will be rather a nightmare
to integrate into the CI pipeline, also all release related activities like code freeze will be complicated, and so on.
Regards,
Andrey
[1]
https://github.com/eclipse-jdtls/eclipse-jdt-core-incubator/discussions/1881
On Tuesday 18 November 2025 19:40:43 (+01:00), Mickael Istria via jdt-dev wrote:
Hello JDT,
To clarify the work being potentially useful in parallel and independently of JDT-LS, we're considering moving the JDT-Javac repo as a subproject of JDT in general, and thus as a sibling of JDT-LS.
This would then be a different subproject, with a different schedule, committers set, GitHub oraganization than "main" JDT. This project would not participate to JDT, Eclipse SDK nor Simrel for the moment; it would basically only host code + CI.
Is there any objection against this move?
We will soon start to work on a project proposal. Your questions/comments/concerns are already more than welcome in order to ensure they are covered as part of the proposal. So please share anything you think can challenge or confort the future proposal.
Thanks!
--
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
--
Kind regards,
Andrey Loskutov
https://www.eclipse.org/user/aloskutov
Спасение утопающих - дело рук самих утопающих
