Installation refused without given a reason

[stephan-herrmann]

1. Install Eclipse SDK from from https://download.eclipse.org/eclipse/downloads/drops4/I20240827-1800/ (exactly)
2. Try to install the patch feature(s) from https://download.eclipse.org/eclipse/updates/4.33-P-builds/P20240903-0810

Installation is rejected saying:

"Eclipse JDT (Java Development Tools) Patch with Java 23 support for 2024-09 development stream" is not applicable to the current configuration and will not be installed.

Neither in this message nor in the error log could I find any reason for the reported incompatibility.

With some experimenting I could figure out that not finding two bundles from org.commonmark was the reason.

To wit:

3. Install "Orbit Maven BND org.commonmark 4.33" from https://download.eclipse.org/tools/orbit/simrel/orbit-aggregation/release/4.33.0
   • to be safe install both same-named artifacts, since we can't see which is source which is binary :)
4. After restart try again step (2) ==>> SUCCESS

It would save a lot of time, if the missing requirement were spelled out in the error message, as it usually happens / happened.

[laeubi]

@stephan-herrmann this usually happens when there is some a strict requirement so it is "impossible" to satisfy especially if one uses patch features so P2 does not know whats exactly wrong, I would read the message as "you try to patch something that is not installed"...

[stephan-herrmann]

I would read the message as "you try to patch something that is not installed"...

That's not what happened in this case.

All plugins included in the patch were present alright in the current installation. One of these plugins was org.eclipse.jdt.core.manipulation, where the new version has regular dependencies on two plugins that were nowhere to be found.

Looking from the outside I see no reason why P2 should be unaware that the problem was a regular unsatisfied dependency, unless the patch feature sends P2 into a totally different mode.

[laeubi]

Patch features are rather special, so it is totally possible that if something is missing for the patch (==> nowhere to be found) that P2 assumes this patch is not applicable.

[stephan-herrmann]

P2 assumes

any chances to make P2 smarter in this regard?

BTW, seeing "not applicable to the current configuration" I initially thought that some plugin might require a JDK newer than the current. Just to illustrate my level of confusion :-/