Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 357510

Summary: Feature patch update succeeds with "install new software" but fails with "Check for updates"
Product: [Eclipse Project] Equinox Reporter: Terry Parker <tparker>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Linux   
Whiteboard: stalebug
Attachments:
Description Flags
JDT feature patch "gg2"
none
JDT feature patch "gg3"
none
p2 metadata folder none

Description Terry Parker CLA 2011-09-13 11:16:30 EDT
Build Identifier: I20110613-1736

Updating from an installed feature patch to a newer version of the feature patch succeeds if done via "Install new software", but is blocked by a "X is not applicable to the current configuration and will not be installed" message when attempting to update via "Check for updates".

Reproducible: Always

Steps to Reproduce:
1. Start with the classic Eclipse distribution for 32-bit Linux
2. Install the initial feature patch in the a.zip repo in attachment #1 [details]
3. Restart Eclipse and validate that the JDT patch was installed
4. Add the b.zip repo to the list of available update sites, and validate that it loads
5. Issue a Help > Check for Updates.  The update can not be applied, yielding a "Google JDT Bugfixes is not applicable to the current configuration and will not be installed" message
6. Issue a Help > Install New Software command, selecting the b.zip archive.  Unselect "group by category".  You can successfully install the feature patch update this way.
Comment 1 Terry Parker CLA 2011-09-13 11:22:55 EDT
Created attachment 203258 [details]
JDT feature patch "gg2"
Comment 2 Terry Parker CLA 2011-09-13 11:24:01 EDT
Created attachment 203259 [details]
JDT feature patch "gg3"
Comment 3 Terry Parker CLA 2011-09-13 11:24:52 EDT
Created attachment 203261 [details]
p2 metadata folder
Comment 4 Terry Parker CLA 2015-02-19 18:54:02 EST
We moved to using the CBI to rebuild Eclipse features with critical cherry picks and no longer use feature patches.

I believe this bug still exists, but it is no longer a priority for my team to fix it. Given that this bug hasn't received any attention and the bug reporter (me) no longer considers it a high priority, I'm fine if this bug is closed as "Won't fix".
Comment 5 Eclipse Genie CLA 2018-12-06 12:44:10 EST
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.
Comment 6 Lars Vogel CLA 2019-09-04 01:49:43 EDT
This bug was marked as stalebug a while ago. Marking as worksforme.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.