Dear Mickael,
What are the consequences if one
eclipse project is "subproject" of another?
IMO, for this case, it's more a matter of highlighting some important relationship between the various projects, and highlighting that JDT-LS (or JDT-Javac) are downstream of JDT.
Where is it legally
defined?
"""
Projects are where the real work happens. Each project has code,
committers, and resources including a website, source code repositories,
space on the build and download server, etc. Projects may act as a
parent for one or more child projects. Each child project has its own
identity, committers, and resource. Projects may, but do not
necessarily, have a dedicated website. Projects are sometimes referred
to as
subprojects or as
components. The
Eclipse Foundation Development Process, however, treats the terms
project,
subproject, and
component as equivalent.
"""
The only effect that i am aware is the mentioning on [1] as
subproject in the "Project hierarchy".
Concretely yes, but this is a strong symbol and hint about how the ecosystem is organized.
That seems wrong. Neither JDT LS nor
JAVAC should be listed as subproject but as total different,
independent project.
This is more an opinion that a fact. That decision to get JDT-LS a subproject of has seemed right to JDT project leads so far as they approved it initially (this is required for creation of subproject). Maybe go though the Creation Review for
eclipse.jdt.ls and surrounding discussions to read the arguments that made the PLs agree with that (basically the expected, and confirmed, positive influence of JDT-LS on the overall situation of JDT).
IMO, same arguments apply to the JDT-Javac case.
And then no objection from JDT can be made.
JDT project leads are allowed to object at creation (actually they're required to agree at creation), and can probably object later to get the case rediscussed with EMO.
