| Re: [cross-project-issues-dev] Attention: Help webapp requires org.eclipse.jdt.core |
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...
Hey everyone,In an effort to fix the help system working on Java 17+ ( https://github.com/eclipse-platform/eclipse.platform.ua/issues/18 ) dependency on org.eclipse.jdt.core (which itself brings org.eclipse.core.resources and etc.).
Please test your plugins and especially RCP applications against latest I-build (https://download.eclipse.org/eclipse/downloads/index.html ) whether this creates any issue for you so we can act prior to M3 release in a week.
--
Aleksandar KurtakovRed Hat Eclipse Team
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev