User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.4.1
Thank you for clarification, Aleksandar!
Indeed, copy of ecj is in fact already forms circular dependency.
However, org.eclipse.jdt.core + dependencies looks much more
monumental.
Interesting, Help subsystem seems to be the main driver of [major]
changes in Platform requirements in recent years.
Does it mean that now we have circular dependency between
Platform and JDT?
It has always been there just hidden by copied old ecj in
org.apache.jasper.glassfish.
Regards,
AF
11/3/2022 5:48 PM, Ed Merks пишет:
As I mentioned on that thread, which is rather long
and meandering (because of me), cross-projects is not
likely to be representative of the overall downstream
community of application developers.
The bottom line is that the JSP support that is
needed for a functioning Help system will work if and
only if you have org.eclipse.jdt.core or org.eclipse.jdt.batch.compiler
installed.
The former has these dependencies with team.core
being optional greedy so will tend to be installed too
unless steps are taken to ensure it's not visible:
While the latter is self-contained and has no
additional dependencies:
The change that has been committed for 4.26 forces
org.eclipse.jdt.core to be installed rather than the
smaller self-contained org.eclipse.jdt.batch.compiler
thereby forcing all RCP applications that use Help to
install core.filesystem, core.resource, text, and
typically team.core (and whatever those require)
whether they want/need those or not.
There is no ideal out-of-the-box solution at this
point, and I thank Aleksandar for his effort on this
front. That being said, I'm personally not
convinced that we should take away the choice
for downstream consumers, even if no one on cross
projects cares nor is affected...