Bug 514077 - Subclipse plugin nonfunctional after update.
Summary: Subclipse plugin nonfunctional after update.
Keywords:
Status: CLOSED DUPLICATE of bug 458626
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 11
Hardware: All
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Andrew Overholt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-27 21:31 UTC by August Schwerdfeger
Modified: 2009-08-20 12:04 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-08-20 12:04:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description August Schwerdfeger 2009-07-27 21:31:47 UTC
Description of problem:

After an update of the package "eclipse-pde" to version 3.4.2-13, the Subclipse plugin, allowing the use of Subversion within Eclipse, becomes nonfunctional. Attempts to rectify this problem by starting Eclipse to a fresh workspace directory have proven fruitless.


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

eclipse-pde-3.4.2-13.fc11.x86_64 (freshly updated)
eclipse-subclipse-1.6.0-1.fc11.noarch (not freshly updated)

Steps to Reproduce:
1. Update to the new version of Eclipse.
2. Start Eclipse.
3. Attempt to use the Subclipse plugin in any way.
  
Actual results:

The presence of the Subclipse plugin is not recognized. The option to check a project out from Subversion does not appear in the "New Project" dialog, and the version data of existing Subversion projects is not displayed.

Expected results:

The presence of the Subclipse plugin is recognized. Version data in existing projects appears, and new Subversion projects can be checked out.

Comment 1 Andrew Overholt 2009-07-27 23:36:29 UTC
Try running with -clean or moving ~/.eclipse out of the way.

Comment 2 August Schwerdfeger 2009-07-28 02:42:04 UTC
I tried moving ~/.eclipse out of the way, which appeared to fix the problem, but then it recurred the next time I launched Eclipse. I moved it again and it seems to be working now.

Comment 3 Alexander Kurtakov 2009-08-20 12:04:34 UTC

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


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