Community
Participate
Working Groups
Created attachment 184811 [details] p2 repo If a patch conflicts with something in the current install and can not be applied, there is no explanation about this conflict in the UI. There is just a simple message "patch is not applicable to the current configuration and will not be installed." To reproduce, start with Eclipse SDK 3.6.1 Find attached a p2 repository containing 2 feature patches. "RCP Patch" (org.eclipse.rcp.R361patch.feature.group) and "RCP Patch V2" (org.eclipse.rcp.R361patchV2.feature.group) Both are attempting to change the version of org.eclipse.equinox.launcher used by the 3.6.1 SDK The first patch does not apply because there are other IUs in the product that have requirements on the launcher. So this patch would introduce conflicts with those IUs. We should expect an explanation saying something about the new version of org.eclipse.equinox.launcher conflicting with the old one and the old one is still required by other IUs. The second patch has been modified by hand to patch these other IUs as well and so it does apply.
This is a known issue and result from the way we are dealing with patches in the UI (and other places). To allow for the patches to uninstalled automatically and thus not block an update to a more recent version of something patched, the patches are installed optionally. This has the side effect that if it can't be applied the planner will return success and the UI will not say anything. Daniel and I have discussed that in the past and in order to address this properly, we would have to do some serious changes to the encoding, especially if we wanted to keep the ability of auto-update that I was describing before.
*** Bug 262736 has been marked as a duplicate of this bug. ***
I'm trying to install an update to an existing JDT feature patch. I can install it successfully if I use "Install new software", but it fails if I use "Check for updates" with the "patch is not applicable to the current configuration and will not be installed" message. Is that this bug or a separate issue?
This would be another bug. Please open it and attach the profile of the install in which you are trying to install, as well as the metadata repo site you are installing the update from.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
