Bug 814963
Summary: | Package lets Eclipse update fail when installed | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bas Mevissen <abuse> |
Component: | eclipse-wtp-servertools | Assignee: | Vladimir Kostadinov <vladimir.kostadinov> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | akurtako, kdaniel, vladimir.kostadinov |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-07 06:57:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bas Mevissen
2012-04-21 16:23:52 UTC
How do you try to update? Using the internal eclipse update? It's never a good idea do mix rpm and update site for the same plugin. Yes, using the Eclipse intenal update. I was under the impression that the plugins installed as a package would simply be excluded from that internal update. Plugins from rpm packages should only get their updates from the yum repository. A functional internal Eclipse update is needed as one might install additional plugins. In my case the Android plugin. So in this case it's the org.eclipse.wst.server.ui missing from Fedora being the problem, right? Can you try on Fedora 17 as this should be fixed as I installed Android tools without a problem on F-17 alpha a month ago? I can do that after next week. But I'm curious what that would bring. I don.t see any relation with the Android plugin. The problem is with the wst server tools on Fedora 16 and apparently not on 17. So maybe a quick compare between the fc16 and fc17 packages by an expert might reveal the problem (I'm currently travelling). F17 seems fine here as well. So what worked on F17 should go to F16 as well. This is not as easy as said because in F17 we have the whole eclipse stack updated and doing that for F16 will be major disruption because of the number of updates needed - every eclipse* package + a number of underlying libraries. Closing the bug as next release as doing this kind of updates will actually make F16 become F17 from Java POV. So there are basically two workarounds: 1) Deselect the packages in the Eclipse update dialog to be able to update non-packages eclipse plugins 2) Remove the package from the system when you don't need it. (2a: one might install the package from a different source, untested) Thanks for looking into this problem and giving the clarification for the closure. |