Bug 773380 - Yesterdays update to 3.7.1-7 broke most functionality (JDT, Subclipse, etc)
Summary: Yesterdays update to 3.7.1-7 broke most functionality (JDT, Subclipse, etc)
Keywords:
Status: CLOSED DUPLICATE of bug 760454
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 16
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Alexander Kurtakov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-11 17:34 UTC by Charles Butterfield
Modified: 2012-01-11 22:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-11 17:51:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Charles Butterfield 2012-01-11 17:34:52 UTC
Description of problem:  Yesterday I did a routine yum update which updated my eclipse components (platform, swt, rcp, jdt) from 3.7.1-4 to 3.7.1-7.  This caused major breakage - lots of error messages at startup, missing perspectives (Java), loss,   I didn't capture all of the details at the time, but see steps to reproduce below.


Version-Release number of selected component (if applicable): 3.7.1-7


How reproducible: Totally


Steps to Reproduce:
1. yum erase eclipse*
2. yum install eclipse-jdt
3. run eclipse
4. New Project does not have a Java project as an option
  
Actual results:
No "Java Project" support

Expected results:
Naturally we would expect "Java Project"

Additional info:

Comment 1 Andrew Overholt 2012-01-11 17:51:47 UTC
This situation occurs because we had to break a packaging loop by moving a plugin from eclipse-jdt to eclipse-platform. Unfortunately, without invasive, fragile workarounds, the only way to fix this is to stop Eclipse, mv ~/.eclipse{,.bak2011-12-21} and restart Eclipse. Some user preferences may be lost and plugins you manually installed (qt, it sounds like) will be gone but you should get the RPM-installed plugins back and you'll be able to re-install anything you previously installed from within Eclipse.

We apologize for this issue and are working on a more robust solution to ensure it never happens again.

*** This bug has been marked as a duplicate of bug 760454 ***

Comment 2 Charles Butterfield 2012-01-11 22:01:08 UTC
Yes, nuking my .eclipse tree did the trick.
Thanks!
-- Charlie


Note You need to log in before you can comment on or make changes to this bug.