Bug 510010
Summary: | Java perspective gone from Eclipse | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nadav Har'El <nyh> |
Component: | eclipse | Assignee: | Andrew Overholt <overholt> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | akurtako, eric, oliver, overholt |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-07-20 07:39:38 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nadav Har'El
2009-07-07 12:11:53 UTC
I am experiencing the same issue, though I've had Fedora 11 since the start. Eclipse Java worked fine until I updated on July 3: Jul 03 14:41:16 Updated: 1:eclipse-swt-3.4.2-11.fc11.x86_64 Jul 03 14:41:17 Updated: 1:eclipse-rcp-3.4.2-11.fc11.x86_64 Jul 03 14:41:27 Updated: 1:eclipse-platform-3.4.2-11.fc11.x86_64 Jul 03 14:42:27 Updated: 1:eclipse-jdt-3.4.2-11.fc11.x86_64 Jul 03 14:42:33 Updated: 1:eclipse-pde-3.4.2-11.fc11.x86_64 Previously, I had been using the -9 builds of these packages successfully. It seems something in the -11 build broken Java editing...no Java perspective, no Java options, etc. Downgrading to the -9 builds restores Java and svn functionality, so it's definitely something in the -11 build: yum downgrade eclipse-swt eclipse-rcp eclipse-platform eclipse-jdt eclipse-pde This is probably the same bug as the one reported in bug 509616 Yeah, this bug is very unfortunate but we are focusing on getting the 3.5 series ready which is no longer affected by this bug. Basically, we try to avoid updates :( Sorry we had one in this case and that you were affected by it. Thankfully running "eclipse -clean" solves the problem, as noted in bug 509616. Thanks. *** This bug has been marked as a duplicate of bug 509616 *** |